Devices and methods for efficient emergency calling

ABSTRACT

Disclosed are devices, systems, methods, and media for efficient emergency calling using digital devices. In some embodiments, a user is able to make an emergency call by a one-touch or dual-touch process. An authentication process may reduce inadvertent and unauthorized emergency calling. Persistent emergency buttons are also disclosed that may be used for calling emergency in different states of the device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/268,664 filed on Dec. 17, 2015, the entire contents of which areincorporated herein by reference.

BACKGROUND

Emergency victims or bystanders may request help by calling a designatedemergency number (e.g., 911 or phone number of a local emergencydispatch center). Increasingly, calls to emergency dispatch centers(“EDCs”), such as Public Safety Answering Points (“PSAPs”), are made viawireless communication devices rather than from land-based telephonelines. However, users are unable to place an emergency call or send anemergency request using wireless communication devices without having todial a predefined number. In addition, when a wireless communicationdevice is used for the emergency call via a cellphone carrier, the EDCsor PSAPs often receive limited location information, which may delay theemergency response time.

SUMMARY

In emergency situations, being able to make an emergency call with acommunication device in a simple and efficient manner can save lives andreduce property damage. Various obstacles may complicate an attempt torequest emergency assistance. An emergency may occur while thecommunication device is in an inaccessible or inconvenient state. Thedevice may in a power-saving state, locked for security reasons,inactive due to low battery life or low cellular signal, or some otherstate that makes it difficult for a user to quickly and easily accessthe device to make an emergency request or call. For example, the usermay not have a soft touch button or interactive element available tomake an emergency call because the display is turned off. Even when thedisplay is on, the user may have to unlock the screen before being ableto place the call. Moreover, the act of calling itself can be a burdendepending on the level of stress the user is experiencing. For example,even dialing a simple number like 9-1-1 requires three consecutiveinteractions to be accurately made, which may be particularly burdensomefor a user in a state of panic or distress (e.g., the user isexperiencing a medical emergency).

However, simplifying the process of making an emergency call or requestis difficult because it may increase the likelihood of inadvertentemergency calls. Inadvertent or prank calling for emergency services canbe burdensome and even a punishable offense in certain jurisdictions.One estimate is that two out of five 9-1-1 calls are accidents, prankcalls, or hang ups, which needlessly depletes emergency responseresources. Therefore, the need to reduce this drain on emergencyresponse resources incentivizes increasing the number of userinteractions with the communication device before the emergency requestis sent in order to minimize accidental dials.

One advantage of the devices, platforms, media, and methods describedherein is that they provide a simple and efficient process for sendingan emergency alert or emergency request. This process allows a user toreach emergency response resources with minimal effort through one ormore user interactions with the communication device that are easy toremember and carry out even in a state of stress. In some embodiments,this process is readily accessible regardless of the state the device isin. For example, in some embodiments, a user is able to send anemergency alert even if the device is in an “inactive” mode in which thedisplay is turned OFF. Another advantage is the process mitigates therisk of sending emergency alerts inadvertently by providing userauthentication. In addition, in some embodiments, the interactionsrequired to send an emergency alert is predefined in a manner to reducethe risk of accidental dialing is reduced. Yet another advantage is theemergency alert itself provides relevant information about the emergencysuch as, for example, user identification, location information, thetype of emergency.

In one aspect, provided herein is a device comprising at least oneprocessor, a memory, a network component, a location component, a userinterface, a display, and instructions executable by the at least oneprocessor to create an application for sending an emergency alertcomprising: (a) an interface module receiving from the user interfaceone or more user interactions indicative of an emergency; (b) acommunication module establishing a communication link with an emergencymanagement system or an emergency dispatch center after the interfacemodule receives the one or more user interactions indicative of anemergency, wherein establishing the communication link comprises sendingan emergency alert comprising a request for emergency assistance andemergency data comprising location information; (c) an authenticationmodule providing user authentication, wherein user authentication isrequired before sending the emergency alert; and (d) at least two devicemodes comprising: (i) an active mode characterized by the display beingpowered on and presenting one or more non-physical interactive elements,wherein the one or more user interactions indicative of an emergencycomprises interacting with one or more non-physical interactive elementson the display; and (ii) an inactive mode characterized by the displaybeing powered off and presenting no interactive elements, wherein theone or more user interactions indicative of an emergency comprisesinteracting with one or more physical interactive elements on thedevice. In some embodiments, the authentication module provides userauthentication by receiving user input authenticating user identity. Infurther embodiments, the user input is selected from the groupconsisting of: name, birth date, social security number, driver licensenumber, home address, email address, phone number, credit cardinformation, bank account information, biometrics, fingerprint, or anycombination thereof. In some embodiments, the authentication moduleevaluates whether authentication is required. In some embodiments, theauthentication module does not require authentication if the risk ofinadvertent emergency calls is low. In some embodiments, theauthentication module does not require authentication if the emergencymanagement system or emergency dispatch center does not requireauthentication. In some embodiments, a user optionally disables theauthentication requirement. In some embodiments, a delay timer isinitiated after the interface module receives one or more userinteractions indicative of an emergency, wherein the communicationmodule sends the emergency alert when the delay timer counts down tozero. In further embodiments, the display presents the delay timer as acountdown during which a user can cancel the communication link beforethe countdown finishes. In further embodiments, the time delay is about10 seconds. In some embodiments, the device further comprises amicrophone for receiving audio input or commands from a user. In someembodiments, the device further comprises a camera for receiving photoor video input from a user. In some embodiments, the authenticationmodule requires one or more user interactions providing userauthentication after the interface module receives one or more userinteractions indicative of an emergency. In further embodiments, the oneor more user interactions providing user authentication is selected fromthe group consisting of: touch, tap, press, squeeze, swipe, voice,gesture, capturing a photo or video with a camera, or any combinationthereof. In some embodiments, the one or more user interactionsindicative of an emergency comprises a live video or photo captured by acamera. In further embodiments, the authentication module analyzes thevideo or photo to provide user authentication through face recognition,body recognition, audio recognition, or a combination thereof. In someembodiments, the one or more user interactions indicative of anemergency is predefined by a user. In some embodiments, the user selectsone or more user interactions from a list of user interactions to berecognized by the interface module as being indicative of an emergency.In some embodiments, the user customizes one or more user interactionsto be recognized by the interface module as being indicative of anemergency. In some embodiments, the one or more user interactionsindicative of an emergency provides user authentication. In someembodiments, the one or more user interactions indicative of anemergency is selected from the group consisting of: touch, tap, press,squeeze, swipe, voice, gesture, capturing a photo or video with acamera, or any combination thereof. In some embodiments, the one or moreuser interactions indicative of an emergency comprises interacting withone or more hard buttons on the device. In further embodiments, the oneor more hard buttons provide biometric authentication. In furtherembodiments, the one or more hard buttons comprise a fingerprint readerproviding fingerprint authentication when the user interacts with theone or more hard buttons. In some embodiments, the one or more userinteractions indicative of an emergency comprises interacting with oneor more hard buttons on the device in a specific sequence. In someembodiments, the one or more user interactions indicative of anemergency comprise one or more voice commands. In further embodiments,the authentication module provides user authentication using voicerecognition of the one or more voice commands. In some embodiments, thedisplay comprises a touchscreen. In some embodiments, the deviceswitches from inactive mode to active mode when the interface modulereceives one or more user interactions indicative of an emergency. Insome embodiments, the active mode is characterized by the displaypresenting without interruption a persistent emergency button throughoutthe duration of the active mode, said persistent emergency buttoncomprising at least one non-physical interactive element indicative ofan emergency. In further embodiments, the interface module receives oneor more interactions indicative of an emergency when the persistentemergency button is selected. In further embodiments, the persistentemergency button is responsive to user interaction when the device islocked. In further embodiments, the persistent emergency button isresponsive to user interaction when the device is in a non-communicativestate. In further embodiments, the persistent emergency button isresponsive to user interaction when the device is engaged with otherfunctions. In yet further embodiments, the other functions are selectedfrom the group consisting of: phone call, messaging, social media, mapor navigation, video chat, VoIP, web browsing, podcast, gaming, watchingvideos, mobile application, or any combination thereof. In furtherembodiments, the persistent emergency button is user adjustable. In yetfurther embodiments, a transparency or opaqueness of the emergencybutton is user adjustable. In yet further embodiments, the position ofthe emergency button on the display is user adjustable. In someembodiments, the display of the device in active mode presentsinteractive elements depicted as a grid of buttons, each interactiveelement corresponding to a different emergency indication. In furtherembodiments, the emergency indications are medical, police, fire, andcar crash, wherein each interactive element comprises a minimalistgraphic depicting the corresponding emergency indication. In someembodiments, the one or more user interactions indicative of anemergency for the device in active mode further comprises interactingwith one or more physical interactive elements on the device. In someembodiments, the device further comprises an emergency modecharacterized by an established communication link with an emergencymanagement system or emergency dispatch center, wherein the displaypresents one or more interactive communication elements available foruser selection to communicate with the emergency management system oremergency dispatch center. In further embodiments, the one or moreinteractive communication elements comprise a speechless button, whereinthe communication module sends information to the emergency managementsystem or emergency dispatch center indicating the user is unable tospeak upon user selection of the speechless button. In furtherembodiments, the one or more interactive communication elementscomprises a messaging button, wherein the communication module sends amessage entered by a user to the emergency management system oremergency dispatch center upon user selection of the messaging button.In further embodiments, the one or more interactive communicationelements comprises a recording button for capturing and sending a photoor video to the emergency management system or emergency dispatch centerupon user selection of the recording button. In further embodiments, theone or more interactive communication elements comprises a speakerphonebutton for hands-free communication with the emergency management systemor emergency dispatch center upon user selection of the speakerphonebutton. In some embodiments, the one or more physical interactiveelements comprise one or more hard buttons. In further embodiments, theone or more hard buttons is selected from the group consisting of: powerbutton, volume button, home button, navigation button, keyboard button,return button, multitasking button, camera button, or any combinationthereof. In further embodiments, the one or more hard buttons comprise asensor. In yet further embodiments, the sensor is a fingerprint scanner.In some embodiments, the non-physical interactive elements comprise oneor more soft buttons. In further embodiments, the one or more softbuttons comprises a persistent emergency button. In some embodiments,the user interaction indicative of an emergency is a one-touchinteraction. In further embodiments, the one-touch interaction comprisesa user interaction with a soft button indicative of an emergency. In yetfurther embodiments, the one-touch interaction comprises a userinteraction with a persistent emergency button. In further embodiments,the one-touch interaction is selected from the group consisting of:voice command, gesture, or photo or video capture with a camera. In yetfurther embodiments, the gesture is selected from the group consistingof: touch, tap, press, squeeze, or swipe. In further embodiments, theone-touch interaction comprises an extended interaction, wherein theuser maintains contact with the user interface for at least 2 seconds.In yet further embodiments, the extended interaction provides userauthentication. In some embodiments, the one or more user interactionsindicative of an emergency comprise a dual touch interaction. In furtherembodiments, the dual touch interaction provides user authentication. Insome embodiments, the emergency data comprises user authenticationinformation. In some embodiments, the emergency data comprises real-timeuser information. In further embodiments, the real-time user informationis selected from the group consisting of: location, emergency, speed,direction, physiological data, or a combination thereof. In yet furtherembodiments, the physiological data is obtained from one or more sensorsin proximity to the user. In some embodiments, the data compriseshistorical user information. In further embodiments, the historical userinformation is selected from the group consisting of: location, pastemergencies, physiological data, or a combination thereof. In yetfurther embodiments, the device periodically stores location informationobtained from the location component to generate historical locationinformation. In yet further embodiments, the historical user informationcomprises predefined information provided by a user. In still yetfurther embodiments, the predefined user information is selected fromname, sex, gender, age, one or more pre-existing medical conditions,contact information, one or more emergency contacts, one or moredisabilities, height, weight, biometric information, one or more presetlocations the user frequents, or any combination thereof. In someembodiments, the emergency request is sent using Voice over InternetProtocol (VoIP). In some embodiments, the device is a communicationdevice. In some embodiments, the device is a mobile wireless device. Insome embodiments, the device is a tablet. In some embodiments, thedevice is a computer. In some embodiments, the device is a wearabledevice. In some embodiments, the communication module stores theemergency data and repeats attempting to establish a communication linkwhen the request for emergency assistance fails to reach the emergencymanagement system or emergency dispatch center.

In another aspect, provided herein is a system for sending an emergencyalert comprising: a device comprising at least one processor, a memory,a network component, a location component, a user interface, a display,and instructions executable by the at least one processor to create anapplication for sending an emergency alert comprising: (a) an interfacemodule receiving from the user interface one or more user interactionsindicative of an emergency; (b) a communication module establishing acommunication link with an emergency management system or an emergencydispatch center after the interface module receives the one or more userinteractions indicative of an emergency, wherein establishing thecommunication link comprises sending an emergency alert comprising arequest for emergency assistance and emergency data comprising locationinformation; (c) an authentication module providing user authentication,wherein user authentication is required before sending the emergencyalert; and (d) at least two device modes comprising: (i) an active modecharacterized by the display being powered on and presenting one or morenon-physical interactive elements, wherein the one or more userinteractions indicative of an emergency comprises interacting with oneor more non-physical interactive elements on the display; and (ii) aninactive mode characterized by the display being powered off andpresenting no interactive elements, wherein the one or more userinteractions indicative of an emergency comprises interacting with oneor more physical interactive elements on the device. In someembodiments, the authentication module provides user authentication byreceiving user input authenticating user identity. In furtherembodiments, the user input is selected from the group consisting of:name, birth date, social security number, driver license number, homeaddress, email address, phone number, credit card information, bankaccount information, biometrics, fingerprint, or any combinationthereof. In some embodiments, the authentication module evaluateswhether authentication is required. In some embodiments, theauthentication module does not require authentication if the risk ofinadvertent emergency calls is low. In some embodiments, theauthentication module does not require authentication if the emergencymanagement system or emergency dispatch center does not requireauthentication. In some embodiments, a user optionally disables theauthentication requirement. In some embodiments, a delay timer isinitiated after the interface module receives one or more userinteractions indicative of an emergency, wherein the communicationmodule sends the emergency alert when the delay timer counts down tozero. In further embodiments, the display presents the delay timer as acountdown during which a user can cancel the communication link beforethe countdown finishes. In further embodiments, the time delay is about10 seconds. In some embodiments, the device further comprises amicrophone for receiving audio input or commands from a user. In someembodiments, the device further comprises a camera for receiving photoor video input from a user. In some embodiments, the authenticationmodule requires one or more user interactions providing userauthentication after the interface module receives one or more userinteractions indicative of an emergency. In further embodiments, the oneor more user interactions providing user authentication is selected fromthe group consisting of: touch, tap, press, squeeze, swipe, voice,gesture, capturing a photo or video with a camera, or any combinationthereof. In some embodiments, the one or more user interactionsindicative of an emergency comprises a live video or photo captured by acamera. In further embodiments, the authentication module analyzes thevideo or photo to provide user authentication through face recognition,body recognition, audio recognition, or a combination thereof. In someembodiments, the one or more user interactions indicative of anemergency is predefined by a user. In some embodiments, the user selectsone or more user interactions from a list of user interactions to berecognized by the interface module as being indicative of an emergency.In some embodiments, the user customizes one or more user interactionsto be recognized by the interface module as being indicative of anemergency. In some embodiments, the one or more user interactionsindicative of an emergency provides user authentication. In someembodiments, the one or more user interactions indicative of anemergency is selected from the group consisting of: touch, tap, press,squeeze, swipe, voice, gesture, capturing a photo or video with acamera, or any combination thereof. In some embodiments, the one or moreuser interactions indicative of an emergency comprises interacting withone or more hard buttons on the device. In further embodiments, the oneor more hard buttons provide biometric authentication. In furtherembodiments, the one or more hard buttons comprise a fingerprint readerproviding fingerprint authentication when the user interacts with theone or more hard buttons. In some embodiments, the one or more userinteractions indicative of an emergency comprises interacting with oneor more hard buttons on the device in a specific sequence. In someembodiments, the one or more user interactions indicative of anemergency comprise one or more voice commands. In further embodiments,the authentication module provides user authentication using voicerecognition of the one or more voice commands. In some embodiments, thedisplay comprises a touchscreen. In some embodiments, the deviceswitches from inactive mode to active mode when the interface modulereceives one or more user interactions indicative of an emergency. Insome embodiments, the active mode is characterized by the displaypresenting without interruption a persistent emergency button throughoutthe duration of the active mode, said persistent emergency buttoncomprising at least one non-physical interactive element indicative ofan emergency. In further embodiments, the interface module receives oneor more interactions indicative of an emergency when the persistentemergency button is selected. In further embodiments, the persistentemergency button is responsive to user interaction when the device islocked. In further embodiments, the persistent emergency button isresponsive to user interaction when the device is in a non-communicativestate. In further embodiments, the persistent emergency button isresponsive to user interaction when the device is engaged with otherfunctions. In yet further embodiments, the other functions are selectedfrom the group consisting of: phone call, messaging, social media, mapor navigation, video chat, VOID, web browsing, podcast, gaming, watchingvideos, mobile application, or any combination thereof. In furtherembodiments, the persistent emergency button is user adjustable. In yetfurther embodiments, a transparency or opaqueness of the emergencybutton is user adjustable. In yet further embodiments, a position of theemergency button on the display is user adjustable. In some embodiments,the display of the device in active mode presents interactive elementsdepicted as a grid of buttons, each interactive element corresponding toa different emergency indication. In further embodiments, the emergencyindications are medical, police, fire, and car crash, wherein eachinteractive element comprises a minimalist graphic depicting thecorresponding emergency indication. In some embodiments, the one or moreuser interactions indicative of an emergency for the device in activemode further comprises interacting with one or more physical interactiveelements on the device. In some embodiments, the device furthercomprises an emergency mode characterized by an establishedcommunication link with an emergency management system or emergencydispatch center, wherein the display presents one or more interactivecommunication elements available for user selection to communicate withthe emergency management system or emergency dispatch center. In furtherembodiments, the one or more interactive communication elements comprisea speechless button, wherein the communication module sends informationto the emergency management system or emergency dispatch centerindicating the user is unable to speak upon user selection of thespeechless button. In further embodiments, the one or more interactivecommunication elements comprises a messaging button, wherein thecommunication module sends a message entered by a user to the emergencymanagement system or emergency dispatch center upon user selection ofthe messaging button. In further embodiments, the one or moreinteractive communication elements comprises a recording button forcapturing and sending a photo or video to the emergency managementsystem or emergency dispatch center upon user selection of the recordingbutton. In further embodiments, the one or more interactivecommunication elements comprises a speakerphone button for hands-freecommunication with the emergency management system or emergency dispatchcenter upon user selection of the speakerphone button. In someembodiments, the one or more physical interactive elements comprise oneor more hard buttons. In further embodiments, the one or more hardbuttons is selected from the group consisting of: power button, volumebutton, home button, navigation button, keyboard button, return button,multitasking button, camera button, or any combination thereof. Infurther embodiments, the one or more hard buttons comprise a sensor. Inyet further embodiments, the sensor is a fingerprint scanner. In someembodiments, the non-physical interactive elements comprise one or moresoft buttons. In further embodiments, the one or more soft buttonscomprises a persistent emergency button. In some embodiments, the userinteraction indicative of an emergency is a one-touch interaction. Infurther embodiments, the one-touch interaction comprises a userinteraction with a soft button indicative of an emergency. In yetfurther embodiments, the one-touch interaction comprises a userinteraction with a persistent emergency button. In further embodiments,the one-touch interaction is selected from the group consisting of:voice command, gesture, or photo or video capture with a camera. In yetfurther embodiments, the gesture is selected from the group consistingof: touch, tap, press, squeeze, or swipe. In further embodiments, theone-touch interaction comprises an extended interaction, wherein theuser maintains contact with the user interface for at least 2 seconds.In yet further embodiments, the extended interaction provides userauthentication. In some embodiments, the one or more user interactionsindicative of an emergency comprise a dual touch interaction. In furtherembodiments, the dual touch interaction provides user authentication. Insome embodiments, the emergency data comprises user authenticationinformation. In some embodiments, the emergency data comprises real-timeuser information. In further embodiments, the real-time user informationis selected from the group consisting of: location, emergency, speed,direction, physiological data, or a combination thereof. In yet furtherembodiments, the physiological data is obtained from one or more sensorsin proximity to the user. In some embodiments, the data compriseshistorical user information. In further embodiments, the historical userinformation is selected from the group consisting of: location, pastemergencies, physiological data, or a combination thereof. In yetfurther embodiments, the device periodically stores location informationobtained from the location component to generate historical locationinformation. In yet further embodiments, the historical user informationcomprises predefined information provided by a user. In still yetfurther embodiments, the predefined user information is selected fromname, sex, gender, age, one or more pre-existing medical conditions,contact information, one or more emergency contacts, one or moredisabilities, height, weight, biometric information, one or more presetlocations the user frequents, or any combination thereof. In someembodiments, the emergency request is sent using Voice over InternetProtocol (VoIP). In some embodiments, the device is a communicationdevice. In some embodiments, the device is a mobile wireless device. Insome embodiments, the device is a tablet. In some embodiments, thedevice is a computer. In some embodiments, the device is a wearabledevice. In some embodiments, the communication module stores theemergency data and repeats attempting to establish a communication linkwhen the request for emergency assistance fails to reach the emergencymanagement system or emergency dispatch center.

In another aspect, provided herein is non-transitory computer-readablestorage media encoded with a computer program including instructionsexecutable by at least one processor to create an application forsending an emergency alert, the application comprising: (a) an interfacemodule receiving from the user interface or display one or more userinteractions indicative of an emergency; (b) a communication moduleestablishing a communication link with an emergency management system oran emergency dispatch center after the interface module receives the oneor more user interactions indicative of an emergency, whereinestablishing the communication link comprises sending an emergency alertcomprising a request for emergency assistance and emergency datacomprising location information; (c) an authentication module providinguser authentication, wherein user authentication is required before thecommunication link is established; and (d) at least two device modescomprising: (i) an active mode characterized by the display beingpowered on and presenting one or more interactive elements, wherein theone or more user interactions indicative of an emergency comprisesinteracting with one or more non-physical interactive elements on thedisplay; and (ii) an inactive mode characterized by the display beingpowered off and presenting no interactive elements, wherein the one ormore user interactions indicative of an emergency comprises interactingwith one or more physical interactive elements on the device. In someembodiments, the authentication module provides user authentication byreceiving user input authenticating user identity. In furtherembodiments, the user input is selected from the group consisting of:name, birth date, social security number, driver license number, homeaddress, email address, phone number, credit card information, bankaccount information, biometrics, fingerprint, or any combinationthereof. In some embodiments, the authentication module evaluateswhether authentication is required. In some embodiments, theauthentication module does not require authentication if the risk ofinadvertent emergency calls is low. In some embodiments, theauthentication module does not require authentication if the emergencymanagement system or emergency dispatch center does not requireauthentication. In some embodiments, a user optionally disables theauthentication requirement. In some embodiments, a delay timer isinitiated after the interface module receives one or more userinteractions indicative of an emergency, wherein the communicationmodule sends the emergency alert when the delay timer counts down tozero. In further embodiments, the display presents the delay timer as acountdown during which a user can cancel the communication link beforethe countdown finishes. In further embodiments, the time delay is about10 seconds. In some embodiments, the interface module receives one ormore user interactions indicative of an emergency comprising audio inputor commands from a microphone. In some embodiments, the interface modulereceives one or more user interactions indicative of an emergencycomprising photo or video input from a camera. In some embodiments, theauthentication module requires one or more user interactions providinguser authentication after the interface module receives one or more userinteractions indicative of an emergency. In further embodiments, the oneor more user interactions providing user authentication is selected fromthe group consisting of: touch, tap, press, squeeze, swipe, voice,gesture, capturing a photo or video with a camera, or any combinationthereof. In some embodiments, the one or more user interactionsindicative of an emergency comprises a live video or photo captured by acamera. In further embodiments, the authentication module analyzes thevideo or photo to provide user authentication through face recognition,body recognition, audio recognition, or a combination thereof. In someembodiments, the one or more user interactions indicative of anemergency is predefined by a user. In some embodiments, the user selectsone or more user interactions from a list of user interactions to berecognized by the interface module as being indicative of an emergency.In some embodiments, the user customizes one or more user interactionsto be recognized by the interface module as being indicative of anemergency. In some embodiments, the one or more user interactionsindicative of an emergency provides user authentication. In someembodiments, the one or more user interactions indicative of anemergency is selected from the group consisting of: touch, tap, press,squeeze, swipe, voice, gesture, capturing a photo or video with acamera, or any combination thereof. In some embodiments, the one or moreuser interactions indicative of an emergency comprises interacting withone or more hard buttons on the device. In further embodiments, the oneor more hard buttons provide biometric authentication. In furtherembodiments, the one or more hard buttons comprise a fingerprint readerproviding fingerprint authentication when the user interacts with theone or more hard buttons. In some embodiments, the one or more userinteractions indicative of an emergency comprises interacting with oneor more hard buttons on the device in a specific sequence. In someembodiments, the one or more user interactions indicative of anemergency comprise one or more voice commands. In further embodiments,the authentication module provides user authentication using voicerecognition of the one or more voice commands. In some embodiments, thedisplay comprises a touchscreen. In some embodiments, the applicationswitches from inactive mode to active mode when the interface modulereceives one or more user interactions indicative of an emergency. Insome embodiments, the active mode is characterized by the displaypresenting without interruption a persistent emergency button throughoutthe duration of the active mode, said persistent emergency buttoncomprising at least one non-physical interactive element indicative ofan emergency. In further embodiments, the interface module receives oneor more interactions indicative of an emergency when the persistentemergency button is selected. In further embodiments, the persistentemergency button is responsive to user interaction when the device islocked. In further embodiments, the persistent emergency button isresponsive to user interaction when the device is in a non-communicativestate. In further embodiments, the persistent emergency button isresponsive to user interaction when the device is engaged with otherfunctions. In yet further embodiments, the other functions are selectedfrom the group consisting of: phone call, messaging, social media, mapor navigation, video chat, VoIP, web browsing, podcast, gaming, watchingvideos, mobile application, or any combination thereof. In furtherembodiments, the persistent emergency button is user adjustable. In yetfurther embodiments, a transparency or opaqueness of the emergencybutton is user adjustable. In yet further embodiments, a position of theemergency button on the display is user adjustable. In some embodiments,the display of the device in active mode presents interactive elementsdepicted as a grid of buttons, each interactive element corresponding toa different emergency indication. In further embodiments, the emergencyindications are medical, police, fire, and car crash, wherein eachinteractive element comprises a minimalist graphic depicting thecorresponding emergency indication. In some embodiments, the one or moreuser interactions indicative of an emergency for the device in activemode further comprises interacting with one or more physical interactiveelements on the device. In further embodiments, the application furthercomprises an emergency mode characterized by an establishedcommunication link with an emergency management system or emergencydispatch center, wherein the display presents one or more interactivecommunication elements available for user selection to communicate withthe emergency management system or emergency dispatch center. In furtherembodiments, the one or more interactive communication elements comprisea speechless button, wherein the communication module sends informationto the emergency management system or emergency dispatch centerindicating the user is unable to speak upon user selection of thespeechless button. In further embodiments, the one or more interactivecommunication elements comprises a messaging button, wherein thecommunication module sends a message entered by a user to the emergencymanagement system or emergency dispatch center upon user selection ofthe messaging button. In further embodiments, the one or moreinteractive communication elements comprises a recording button forcapturing and sending a photo or video to the emergency managementsystem or emergency dispatch center upon user selection of the recordingbutton. In further embodiments, the one or more interactivecommunication elements comprises a speakerphone button for hands-freecommunication with the emergency management system or emergency dispatchcenter upon user selection of the speakerphone button. In someembodiments, the one or more physical interactive elements comprise oneor more hard buttons. In further embodiments, the one or more hardbuttons is selected from the group consisting of: power button, volumebutton, home button, navigation button, keyboard button, return button,multitasking button, camera button, or any combination thereof. Infurther embodiments, the one or more hard buttons comprise a sensor. Inyet further embodiments, the sensor is a fingerprint scanner. In someembodiments, the non-physical interactive elements comprise one or moresoft buttons. In further embodiments, the one or more soft buttonscomprises a persistent emergency button. In some embodiments, the userinteraction indicative of an emergency is a one-touch interaction. Infurther embodiments, the one-touch interaction comprises a userinteraction with a soft button indicative of an emergency. In yetfurther embodiments, the one-touch interaction comprises a userinteraction with a persistent emergency button. In further embodiments,the one-touch interaction is selected from the group consisting of:voice command, gesture, or photo or video capture with a camera. In yetfurther embodiments, the gesture is selected from the group consistingof: touch, tap, press, squeeze, or swipe. In further embodiments, theone-touch interaction comprises an extended interaction, wherein theuser maintains contact with the user interface for at least 2 seconds.In yet further embodiments, the extended interaction provides userauthentication. In some embodiments, the one or more user interactionsindicative of an emergency comprise a dual touch interaction. In furtherembodiments, the dual touch interaction provides user authentication. Insome embodiments, the emergency data comprises user authenticationinformation. In some embodiments, the emergency data comprises real-timeuser information. In further embodiments, the real-time user informationis selected from the group consisting of: location, emergency, speed,direction, physiological data, or a combination thereof. In yet furtherembodiments, the physiological data is obtained from one or more sensorsin proximity to the user. In some embodiments, the data compriseshistorical user information. In further embodiments, the historical userinformation is selected from the group consisting of: location, pastemergencies, physiological data, or a combination thereof. In yetfurther embodiments, the application periodically stores locationinformation obtained from the location component to generate historicallocation information. In yet further embodiments, the historical userinformation comprises predefined information provided by a user. Instill yet further embodiments, the predefined user information isselected from name, sex, gender, age, one or more pre-existing medicalconditions, contact information, one or more emergency contacts, one ormore disabilities, height, weight, biometric information, one or morepreset locations the user frequents, or any combination thereof. In someembodiments, the emergency request is sent using Voice over InternetProtocol (VoIP). In some embodiments, the application is run on acommunication device. In some embodiments, the application is run on amobile wireless device. In some embodiments, the application is run on atablet. In some embodiments, the application is run on a computer. Insome embodiments, the application is run on a wearable device. In someembodiments, the communication module stores the emergency data andrepeats attempting to establish a communication link when the requestfor emergency assistance fails to reach the emergency management systemor emergency dispatch center.

In another aspect, provided herein is a method of sending an emergencyalert using a communication device comprising at least one processor, amemory, a network component, a location component, a user interface, adisplay, and instructions executable by the at least one processor tocreate an application for sending an emergency alert, the methodcomprising: (a) providing, by the device, an interface module receivingone or more user interactions indicative of an emergency from the userinterface, display, microphone, or camera; (b) establishing, by thedevice, a communication module establishing a communication link with anemergency management system or an emergency dispatch center after theinterface module receives the one or more user interactions indicativeof an emergency, wherein establishing the communication link comprisessending an emergency alert comprising a request for emergency assistanceand emergency data comprising location information; (c) providing, bythe device, an authentication module providing user authentication,wherein user authentication is required before a communication link isestablished; and (d) providing, by the device, at least two device modescomprising: (i) an active mode characterized by the display beingpowered on and presenting one or more interactive elements, wherein theone or more user interactions indicative of an emergency comprisesinteracting with one or more interactive elements on the display; and(ii) an inactive mode characterized by the display being powered off andpresenting no interactive elements, wherein the one or more userinteractions indicative of an emergency comprises interacting with oneor more hard buttons on the device. In some embodiments, theauthentication module provides user authentication by receiving userinput authenticating user identity. In further embodiments, the userinput is selected from the group consisting of: name, birth date, socialsecurity number, driver license number, home address, email address,phone number, credit card information, bank account information,biometrics, fingerprint, or any combination thereof. In someembodiments, the authentication module evaluates whether authenticationis required. In some embodiments, the authentication module does notrequire authentication if the risk of inadvertent emergency calls islow. In some embodiments, the authentication module does not requireauthentication if the emergency management system or emergency dispatchcenter does not require authentication. In some embodiments, a useroptionally disables the authentication requirement. In some embodiments,a delay timer is initiated after the interface module receives one ormore user interactions indicative of an emergency, wherein thecommunication module sends the emergency alert when the delay timercounts down to zero. In further embodiments, the display presents thedelay timer as a countdown during which a user can cancel thecommunication link before the countdown finishes. In furtherembodiments, the time delay is about 10 seconds. In some embodiments,the method further comprises receiving, by the device, audio input orcommands from a user via a microphone. In some embodiments, the methodfurther comprises receiving, by the device, photo or video input from auser via a camera. In some embodiments, the authentication modulerequires one or more user interactions providing user authenticationafter the interface module receives one or more user interactionsindicative of an emergency. In further embodiments, the one or more userinteractions providing user authentication is selected from the groupconsisting of: touch, tap, press, squeeze, swipe, voice, gesture,capturing a photo or video with a camera, or any combination thereof. Insome embodiments, the one or more user interactions indicative of anemergency comprises a live video or photo captured by a camera. Infurther embodiments, the authentication module analyzes the video orphoto to provide user authentication through face recognition, bodyrecognition, audio recognition, or a combination thereof. In someembodiments, the one or more user interactions indicative of anemergency is predefined by a user. In some embodiments, the user selectsone or more user interactions from a list of user interactions to berecognized by the interface module as being indicative of an emergency.In some embodiments, the user customizes one or more user interactionsto be recognized by the interface module as being indicative of anemergency. In some embodiments, the one or more user interactionsindicative of an emergency provides user authentication. In someembodiments, the one or more user interactions indicative of anemergency is selected from the group consisting of: touch, tap, press,squeeze, swipe, voice, gesture, capturing a photo or video with acamera, or any combination thereof. In some embodiments, the one or moreuser interactions indicative of an emergency comprises interacting withone or more hard buttons on the device. In further embodiments, the oneor more hard buttons provide biometric authentication. In furtherembodiments, the one or more hard buttons comprise a fingerprint readerproviding fingerprint authentication when the user interacts with theone or more hard buttons. In some embodiments, the one or more userinteractions indicative of an emergency comprises interacting with oneor more hard buttons on the device in a specific sequence. In someembodiments, the one or more user interactions indicative of anemergency comprise one or more voice commands. In further embodiments,the authentication module provides user authentication using voicerecognition of the one or more voice commands. In some embodiments, thedisplay comprises a touchscreen. In some embodiments, the deviceswitches from inactive mode to active mode when the interface modulereceives one or more user interactions indicative of an emergency. Insome embodiments, the active mode is characterized by the displaypresenting without interruption a persistent emergency button throughoutthe duration of the active mode, said persistent emergency buttoncomprising at least one non-physical interactive element indicative ofan emergency. In further embodiments, the interface module receives oneor more interactions indicative of an emergency when the persistentemergency button is selected. In further embodiments, the persistentemergency button is responsive to user interaction when the device islocked. In further embodiments, the persistent emergency button isresponsive to user interaction when the device is in a non-communicativestate. In further embodiments, the persistent emergency button isresponsive to user interaction when the device is engaged with otherfunctions. In yet further embodiments, the other functions are selectedfrom the group consisting of: phone call, messaging, social media, mapor navigation, video chat, VOID, web browsing, podcast, gaming, watchingvideos, mobile application, or any combination thereof. In furtherembodiments, the persistent emergency button is user adjustable. In yetfurther embodiments, a transparency or opaqueness of the emergencybutton is user adjustable. In yet further embodiments, a position of theemergency button on the display is user adjustable. In some embodiments,the display of the device in active mode presents interactive elementsdepicted as a grid of buttons, each interactive element corresponding toa different emergency indication. In further embodiments, the emergencyindications are medical, police, fire, and car crash, wherein eachinteractive element comprises a minimalist graphic depicting thecorresponding emergency indication. In some embodiments, the one or moreuser interactions indicative of an emergency for the device in activemode further comprises interacting with one or more physical interactiveelements on the device. In further embodiments, the method furthercomprises providing, by the device, an emergency mode characterized byan established communication link with an emergency management system oremergency dispatch center, wherein the display presents one or moreinteractive communication elements available for user selection tocommunicate with the emergency management system or emergency dispatchcenter. In further embodiments, the one or more interactivecommunication elements comprise a speechless button, wherein thecommunication module sends information to the emergency managementsystem or emergency dispatch center indicating the user is unable tospeak upon user selection of the speechless button. In furtherembodiments, the one or more interactive communication elementscomprises a messaging button, wherein the communication module sends amessage entered by a user to the emergency management system oremergency dispatch center upon user selection of the messaging button.In further embodiments, the one or more interactive communicationelements comprises a recording button for capturing and sending a photoor video to the emergency management system or emergency dispatch centerupon user selection of the recording button. In further embodiments, theone or more interactive communication elements comprises a speakerphonebutton for hands-free communication with the emergency management systemor emergency dispatch center upon user selection of the speakerphonebutton. In some embodiments, the one or more physical interactiveelements comprise one or more hard buttons. In further embodiments, theone or more hard buttons is selected from the group consisting of: powerbutton, volume button, home button, navigation button, keyboard button,return button, multitasking button, camera button, or any combinationthereof. In further embodiments, the one or more hard buttons comprise asensor. In yet further embodiments, the sensor is a fingerprint scanner.In some embodiments, the non-physical interactive elements comprise oneor more soft buttons. In further embodiments, the one or more softbuttons comprises a persistent emergency button. In some embodiments,the user interaction indicative of an emergency is a one-touchinteraction. In further embodiments, the one-touch interaction comprisesa user interaction with a soft button indicative of an emergency. In yetfurther embodiments, the one-touch interaction comprises a userinteraction with a persistent emergency button. In further embodiments,the one-touch interaction is selected from the group consisting of:voice command, gesture, or photo or video capture with a camera. In yetfurther embodiments, the gesture is selected from the group consistingof: touch, tap, press, squeeze, or swipe. In further embodiments, theone-touch interaction comprises an extended interaction, wherein theuser maintains contact with the user interface for at least 2 seconds.In yet further embodiments, the extended interaction provides userauthentication. In some embodiments, the one or more user interactionsindicative of an emergency comprise a dual touch interaction. In furtherembodiments, the dual touch interaction provides user authentication. Insome embodiments, the emergency data comprises user authenticationinformation. In some embodiments, the emergency data comprises real-timeuser information. In further embodiments, the real-time user informationis selected from the group consisting of: location, emergency, speed,direction, physiological data, or a combination thereof. In yet furtherembodiments, the physiological data is obtained from one or more sensorsin proximity to the user. In some embodiments, the data compriseshistorical user information. In further embodiments, the historical userinformation is selected from the group consisting of: location, pastemergencies, physiological data, or a combination thereof. In yetfurther embodiments, the device periodically stores location informationobtained from the location component to generate historical locationinformation. In yet further embodiments, the historical user informationcomprises predefined information provided by a user. In still yetfurther embodiments, the predefined user information is selected fromname, sex, gender, age, one or more pre-existing medical conditions,contact information, one or more emergency contacts, one or moredisabilities, height, weight, biometric information, one or more presetlocations the user frequents, or any combination thereof. In someembodiments, the emergency request is sent using Voice over InternetProtocol (VoIP). In some embodiments, the device is a communicationdevice. In some embodiments, the device is a mobile wireless device. Insome embodiments, the device is a tablet. In some embodiments, thedevice is a computer. In some embodiments, the device is a wearabledevice. In some embodiments, the communication module stores theemergency data and repeats attempting to establish a communication linkwhen the request for emergency assistance fails to reach the emergencymanagement system or emergency dispatch center.

In another aspect, provided herein is a method of requesting emergencyassistance by sending an emergency alert using a communication device,the method comprising: (a) providing, by the device, user authenticationthrough pre-registration and SMS verification; (b) receiving, by thedevice, a one touch user interaction indicative of an emergency; (c)initiating, by the device, a countdown for sending an emergency requestto an emergency management system or emergency dispatch center, whereinthe display presents the countdown, a confirm emergency button forsending the emergency request immediately, and an cancel emergencybutton for cancelling the emergency request and countdown; (d)restarting, by the device, the countdown when a user interaction isdetected before the countdown reaches 0; and (e) sending, by the device,the emergency request when the countdown reaches 0 or upon receiving auser interaction with the confirm emergency button.

INCORPORATION BY REFERENCE

All publications, patents, and patent applications mentioned in thisspecification are herein incorporated by reference to the same extent asif each individual publication, patent, or patent application wasspecifically and individually indicated to be incorporated by reference.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features of the invention are set forth with particularity inthe appended claims. A better understanding of the features andadvantages of the present invention will be obtained by reference to thefollowing detailed description that sets forth illustrative embodiments,in which the principles of the invention are utilized, and theaccompanying drawings of which:

FIG. 1A is a schematic diagram of one embodiment of a device foremergency calling;

FIG. 1B is a schematic diagram of one embodiment of an application foremergency calling;

FIG. 2 is a schematic diagram of one embodiment of a communicationdevice displaying a soft button for making an emergency call;

FIG. 3 is a schematic diagram of one embodiment of a communicationdevice displaying a plurality of buttons for making an emergency call;

FIG. 4 is a flowchart of one embodiment showing how a user makes anemergency call using a one-touch button;

FIG. 5 is a schematic diagram of one embodiment of the communicationdevice displaying a persistent emergency button for making an emergencycall in the home screen;

FIG. 6 is a schematic diagram of one embodiment of the communicationdevice displaying a persistent emergency button while a browserapplication is running;

FIG. 7 is a flowchart showing one embodiment of how a user makes anemergency call using a communication device;

FIG. 8 is a schematic diagram of one embodiment of the communicationdevice with a persistent emergency button in the locked screen; and

FIG. 9 is a flowchart showing how a user makes an emergency call with aninactive display in one embodiment of the communication device.

DETAILED DESCRIPTION

Historically, a user has not been able to place a call for requesting anemergency response from an emergency dispatch center (EDC) such as apublic safety access point (PSAP) using a fast and simple process on acommunication device that is accessible regardless of the state of thedevice. A number of personal communication devices are enabled withsoftware applications to call for emergency assistance over datacommunication channels, such as the Internet. However these softwareapplications require an excessive sequence of interactions for the userto send an emergency assistance request. Such software applications mayalso require a user to input a response to a query on the device and towait for the device to respond or act upon that input to continue theprocess of placing a call for emergency assistance. The sequence ofinteractions required to initiate a call for emergency assistance canlead to undesirable delay or even failure to initiate the call. Forexample, the device may become unresponsive during the performance ofthe series of interactions because the user is unable to provideinformation requested by the device (e.g., user panics and forgetspassword, causing the device to be locked after repeatedly entering anincorrect password).

Moreover, a user wishing to place a call requesting an emergencyresponse may find the process overly complicated if using acommunication device in a certain state, such as when the device islocked, the display screen is off, certain applications are open, orsome other device state when the Home Screen is not showing. Forexample, if the device is a smart phone with a touchscreen display thatis turned off, the user may have to first press a button to turn on thetouchscreen. The user may then need to press the home button or swipe inorder to reach the unlock screen. Here, the user then has to enter a 4or 6-digit number combination in order to unlock the device. Next, theuser may need to press a call or phone button on the touchscreen displayto bring up a dial screen, dial the digits 9-1-1, and then press thecall or phone button again to initiate the call. This particular processrequires a precise sequence of at least 11 user interactions, which canbe an onerous burden for a user in the midst of an emergency situation.

Furthermore, an emergency call made in this manner has variousdisadvantages including a lack of accurate location information and aninability for the user to provide additional details and authorizationmechanisms. An emergency dispatch center (“EDC”) that receives anemergency call may have difficulty receiving adequate locationinformation from mobile/wireless communication devices. The EDCpersonnel may also be limited to speaking with the user making the callin order to obtain relevant details of the emergency. In addition, thedesignated emergency number may vary between different countries, andthe user will have to be aware of the correct number in order to make anemergency call. For example, the designated emergency number in theUnited Kingdom is 1-1-2 when dialing from a mobile phone.

The devices, systems, methods, and media described herein enable usersto utilize communication devices to place emergency calls or requests ina fast and simple manner regardless of the state of the communicationdevice.

In some embodiments, described herein are devices comprising at leastone processor, a memory, a network component, a location component, auser interface, a display, and instructions executable by the at leastone processor to create an application for sending an emergency alertcomprising: (a) an interface module receiving from the user interfaceone or more user interactions indicative of an emergency; (b) acommunication module establishing a communication link with an emergencymanagement system or an emergency dispatch center after the interfacemodule receives the one or more user interactions indicative of anemergency, wherein establishing the communication link comprises sendingan emergency alert comprising a request for emergency assistance andemergency data comprising location information; (c) an authenticationmodule providing user authentication, wherein user authentication isrequired before sending the emergency alert; and (d) at least two devicemodes comprising: (i) an active mode characterized by the display beingpowered on and presenting one or more non-physical interactive elements,wherein the one or more user interactions indicative of an emergencycomprises interacting with one or more non-physical interactive elementson the display; and (ii) an inactive mode characterized by the displaybeing powered off and presenting no interactive elements, wherein theone or more user interactions indicative of an emergency comprisesinteracting with one or more physical interactive elements on thedevice.

In some embodiments, described herein are systems for sending anemergency alert comprising: a device comprising at least one processor,a memory, a network component, a location component, a user interface, adisplay, and instructions executable by the at least one processor tocreate an application for sending an emergency alert comprising: (a) aninterface module receiving from the user interface one or more userinteractions indicative of an emergency; (b) a communication moduleestablishing a communication link with an emergency management system oran emergency dispatch center after the interface module receives the oneor more user interactions indicative of an emergency, whereinestablishing the communication link comprises sending an emergency alertcomprising a request for emergency assistance and emergency datacomprising location information; (c) an authentication module providinguser authentication, wherein user authentication is required beforesending the emergency alert; and (d) at least two device modescomprising: (i) an active mode characterized by the display beingpowered on and presenting one or more non-physical interactive elements,wherein the one or more user interactions indicative of an emergencycomprises interacting with one or more non-physical interactive elementson the display; and (ii) an inactive mode characterized by the displaybeing powered off and presenting no interactive elements, wherein theone or more user interactions indicative of an emergency comprisesinteracting with one or more physical interactive elements on thedevice.

In some embodiments, described herein are non-transitorycomputer-readable storage media encoded with a computer programincluding instructions executable by at least one processor to create anapplication for sending an emergency alert, the application comprising:(a) an interface module receiving from the user interface or display oneor more user interactions indicative of an emergency; (b) acommunication module establishing a communication link with an emergencymanagement system or an emergency dispatch center after the interfacemodule receives the one or more user interactions indicative of anemergency, wherein establishing the communication link comprises sendingan emergency alert comprising a request for emergency assistance andemergency data comprising location information; (c) an authenticationmodule providing user authentication, wherein user authentication isrequired before the communication link is established; and (d) at leasttwo device modes comprising: (i) an active mode characterized by thedisplay being powered on and presenting one or more interactiveelements, wherein the one or more user interactions indicative of anemergency comprises interacting with one or more non-physicalinteractive elements on the display; and (ii) an inactive modecharacterized by the display being powered off and presenting nointeractive elements, wherein the one or more user interactionsindicative of an emergency comprises interacting with one or morephysical interactive elements on the device.

In some embodiments, described herein are methods of sending anemergency alert using a communication device comprising at least oneprocessor, a memory, a network component, a location component, a userinterface, a display, and instructions executable by the at least oneprocessor to create an application for sending an emergency alert, themethod comprising: (a) providing, by the device, an interface modulereceiving one or more user interactions indicative of an emergency fromthe user interface, display, microphone, or camera; (b) establishing, bythe device, a communication module establishing a communication linkwith an emergency management system or an emergency dispatch centerafter the interface module receives the one or more user interactionsindicative of an emergency, wherein establishing the communication linkcomprises sending an emergency alert comprising a request for emergencyassistance and emergency data comprising location information; (c)providing, by the device, an authentication module providing userauthentication, wherein user authentication is required before acommunication link is established; and (d) providing, by the device, atleast two device modes comprising: (i) an active mode characterized bythe display being powered on and presenting one or more interactiveelements, wherein the one or more user interactions indicative of anemergency comprises interacting with one or more interactive elements onthe display; and (ii) an inactive mode characterized by the displaybeing powered off and presenting no interactive elements, wherein theone or more user interactions indicative of an emergency comprisesinteracting with one or more hard buttons on the device.

In some embodiments, described herein are methods of requestingemergency assistance by sending an emergency alert using a communicationdevice, the method comprising: (a) providing, by the device, userauthentication through pre-registration and SMS verification; (b)receiving, by the device, a one touch user interaction indicative of anemergency; (c) initiating, by the device, a countdown for sending anemergency request to an emergency management system or emergencydispatch center, wherein the display presents the countdown, a confirmemergency button for sending the emergency request immediately, and ancancel emergency button for cancelling the emergency request andcountdown; (d) restarting, by the device, the countdown when a userinteraction is detected before the countdown reaches 0; and (e) sending,by the device, the emergency request when the countdown reaches 0 orupon receiving a user interaction with the confirm emergency button.

In some embodiments, described herein is a method of facilitatingcommunication between a user of a communication device, for example, awireless communication device or a smart phone, and an EMS or EDCwherein the communication is initiated by limited number of interactions(such as one, dual, triple, etc.) between the user and the communicationdevice. In some embodiments, the method comprises configuring thecommunication device to recognize one or more user interactions, forexample, touch, swipe, voice, tap or other forms of user interactions,as an initiation of a request for emergency assistance from a user ofthe communication device. In some embodiments, the user interaction is aone touch interaction from the user that causes the communication deviceto initiate a call requesting emergency assistance. In otherembodiments, the user interaction is a sequence of two (dual touch) userinteractions. In some embodiments, the communication device uses eithera first or a second user interaction to authenticate or verify theidentity of the user of the communication device. In some embodiments,the communication device sends a request for emergency assistance to anEMS or EDC after user authentication. In some embodiments, the requestcomprises information or data about the user (e.g., user name, healthrecords, emergency contact information, family information, or acombination thereof) that are relevant to emergency response personnelin providing emergency assistance to the user.

In some embodiments, the interaction between the user and thecommunication device includes the user interacting with a touch screenof the communication device capable of displaying soft buttons to theuser. In some embodiments, the communication device is able to recognizewhich soft button the user has selected based on one or more forms ofuser interaction (e.g., interaction via touch, tap, swipe, voice,gesture, face recognition, body recognition or other forms ofuser-device interaction). In some embodiments, based on thisinteraction, the device and/or the software application for emergencycalling determines if a request for emergency assistance should beplaced to the EDC. If so, the device places a call for emergencyassistance. In some embodiments, the communication device utilizes oneor more of voice recognition, gesture recognition, face recognition,body recognition or other forms of user-device interaction to identifyor verify the identity of the user of the communication device andinclude metadata related to the user in the call for emergencyassistance.

In some embodiments the interaction between the user and thecommunication device includes interacting with one or more hard buttonsof the communication device, (e.g., a power button, a volume controlbutton, etc.). In some embodiments, the communication device isconfigured to recognize a particular sequence and/or pattern of pressesof the one or more hard buttons as a command to the communication deviceto send an emergency alert to an EDC on behalf of the user.

In some embodiments, the interaction between the user and thecommunication device authenticates the user of the communication device,following which an emergency alert is sent from the communication deviceto an EMS or EDC. In some embodiments, the interaction between the userand the communication device is used to send an emergency alert from thecommunication device to and EDC without authentication of the request orthe identity of the user.

CERTAIN TERMINOLOGIES

As described herein, a “device” is a digital processing device. In someembodiments, a device is a piece of electronic equipment designed withone or more functionalities. In some embodiments, a “communicationdevice” is any device with a communication component (e.g., networkelement, network component, or any other network or communicationcomponent), which allows it to send and receive information over awireless channel, a wired channel, or a combination thereof. In someembodiments, a communication device makes an emergency call or requestover a communication network such as, for example, a cellular network orthe Internet. In some embodiments, a communication device sends andreceives information over a cellular network or the Internet. In someembodiments, a communication device is a mobile phone, a smart phone, alaptop, a desktop, or a tablet. In some embodiments, a communicationdevice is a wearable device with a communication component. As usedherein, “mobile wireless device” refers to devices that are portable. Insome embodiments, a user wears or carries the mobile wireless device onhis or her person or in a vehicle. Exemplary mobile wireless devicesinclude mobile or cellular phones, wearable devices, etc.

As described herein, an “emergency alert” refers to contacting anemergency service over one or more communication channels or linksregarding an emergency situation. In some embodiments, an emergencyalert comprises an “emergency call” in which a user calls an emergencyservice. In some embodiments, an emergency alert comprises an “emergencyrequest” which a user requests emergency assistance from an emergencyservice. In some embodiments, the emergency service is an emergencymanagement system (“EMS”). In some embodiments, the emergency service isan emergency dispatch center (“EDC”) or public-safety answering point(“PSAP”). In some embodiments, the emergency service is an EMS that actsas an intermediary between the user caller and an EDC or PSAP, wherebythe EMS processes an emergency alert received from the user and forwardsthe request along with relevant information to the appropriate EDC orPSAP. In some embodiments, an “appropriate” EDC or PSAP is one that islocated in the same jurisdiction as the location of the usercommunication device sending the emergency alert.

As described herein, the “state” of a communication device refers to aparticular state in various components of the communication device areat different levels of activity. In some embodiments, the device statedepends on operating systems, customizations and settings of the device,user preferences, usage behavior, power levels or other factors. In someembodiments, the state of a communication device is determined bypre-installed or user predefined settings of the device forpower-saving, security, battery life, cellular signal, satellite signal,etc. For example, in some embodiments, a communication device such as amobile phone is in a flight state, wherein the communication module hasbeen disabled to prevent communication by the phone. In someembodiments, the device is in a sleep or hibernate state, which arepower saving states where various components and applications aredisabled or at lower activity levels. In some embodiments, a device isin a locked state that provides a security measure requiring the user tounlock the device (e.g., by entering a number combination) before beingable to fully access the device.

As described herein, the device has one or more “modes.” An “activemode” refers to when the display is on and presenting one or moreinteractive elements (e.g., soft buttons). In some embodiments, thedisplay is a touchscreen or a standard display, LCD, LED, etc. Asdescribed herein, an “inactive mode” refers to when the communicationdevice is powered on, wherein the display is powered off or showing ablank screen, and presents no interactive elements. In this mode, nointeractive elements are visible or available for interaction. Asdescribed herein, an “emergency mode” refers to the mode of the devicewhen a user has sent an emergency alert (thus establishing acommunication link). In some embodiments, a device is in emergency modeafter sending an emergency alert even when the EMS or EDC fails torespond. In some embodiments, a device in emergency mode displays one ormore interactive elements for enhanced communication with an emergencymanagement system or emergency dispatch center. In some embodiments, adevice in emergency mode displays a message indicating whether theemergency alert was successfully received by an EMS or EDC. In someembodiments, a device in emergency mode periodically re-sends theemergency alert if the previous alert is not successfully received by anEMS or EDC until the user cancels the call or request. In someembodiments, the period the device in emergency mode waits beforere-sending the emergency alert is about 1, 2, 3, 4, 5, 6, 7, 8, 9, 10,11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28,29, 30, 35, 40, 45, 50, 55, or 60 seconds or more after the previousalert is not successfully received by an EMS or EDC. As referencedherein, “stealth mode” refers to a mode in which the emergency alert ismade without detectable cues, for example, without sound.

As referenced herein, a “physical button” and “hard button” aresynonymous and refer to a physical interactive button on a device andnot a non-physical or soft interactive element such as a soft button ona display or touchscreen.

As referenced herein, an “Emergency Management System” (EMS) refers to asystem that receives and processes emergency alerts from users andforwards them to the appropriate EDC, for example, the EDC for thejurisdiction from which the emergency call or request was made. Variousembodiments of the EMS are described in U.S. patent application Ser. No.14/856,818, and incorporated herein by reference. The “EmergencyDispatch Center” (EDC) refers to the entity that receives the emergencyalert and coordinates the emergency assistance. In some embodiments, theEDC is a public organization run by the municipality, county or city ormay be a private organization. In some embodiments, emergency assistanceis selected from medical, caregivers, firefighting, police, military,paramilitary, border patrol, lifeguard, security services, or anycombination thereof. A “public-safety answering point” (PSAP) refers toa call center that answers calls to emergency numbers for police,firefighting, ambulance services, etc.

As used herein, a “user interaction” or “interaction” refers to a userinteracting with a device to provide input. In some embodiments, aninteraction comprises interacting with a physical or non-physicalinteractive element on the device. In some embodiments, a physicalinteractive element is a hard button. In some embodiments, a physicalinteractive element is a camera, a microphone, a fingerprintreader/scanner, a sensor, or any other device component for receivinguser input. In some embodiments, a non-physical interactive element is asoft button on a touchscreen. In some embodiments, an interaction with aphysical or non-physical interactive element comprises touching,tapping, swiping, pressing, squeezing, clicking, turning, rotating,spinning, typing, speaking, or gesturing. In some embodiments, aninteraction has a prolonged duration, for example, pressing a hardbutton for 5 seconds. In some embodiments, a user provides more than oneinteraction by providing two or more consecutive interactions.

Existing filings, for example, U.S. patent application Ser. No.14/856,818, titled “METHOD AND SYSTEM FOR EMERGENCY CALL MANAGEMENT,”filed on Sep. 17, 2015 and incorporated herein by reference, takeadvantage of Voice over Internet Protocol (VoIP) technology to makeemergency calls, including multi-media messaging, from communicationdevices such as cellular phones to EDCs.

FIG. 1A is a schematic diagram of one embodiment of a device describedherein. In some embodiments, the device 102 is an electronic device suchas a communication device (e.g., mobile or cellular phone, computer,laptop, etc.). In some embodiments, a communication device is a wearabledevice. In some embodiments, a communication device is a wireless mobiledevice or a smart phone. In some embodiments, a user 100 is selectedfrom one or more persons who are the primary users of the device 102.

In some embodiments, the device 102 comprises at least one processor115, a memory 119 (e.g., an EPROM memory, a RAM, a solid-state memory),a display 111, a user interface 113, a network component 123 (e.g., anantenna and associated components, Wi-Fi adapters, Bluetooth® adapters,etc.) and a software application 108 (e.g., mobile application, serverapplication, computer program, application). In some embodiments, thewearable device is equipped with a location component 117, for example,a global positioning system (GPS).

User Interface

In some embodiments, the device 102 has several components including adisplay 111 and user interface 113, which allow the user 100 to interactwith the device 102. In some embodiments, the display 111 is a part ofthe user interface 113. In some embodiments, the display 111 and/or theuser interface 113 comprises a touch screen (e.g., a capacitive touchscreen), which is capable of displaying information and receiving userinput. In some embodiments, a touch screen comprises one or morenon-physical interactive elements such as, for example, soft buttons. Asused herein, a soft button refers to a non-physical, simulated buttonshown on a display or touch screen. In some embodiments, a soft buttonis an emergency button, an emergency call button, an emergency selectionbutton, a persistent emergency button, a message button, a text button,a photo button, a video button, a photo/video button, an app button, anemergency app button, or any other soft button. In some embodiments, auser interacts with a non-physical interactive element by touching,tapping, swiping, or pressing the element. In some embodiments, a userinterface 113 comprises one or more physical interactive elements. Insome embodiments, physical interactive elements comprise physical orhard buttons (not shown). In some embodiments, a hard button is a powerbutton, a volume toggle button, a home button, a back button, menubutton, navigation button(s), return button, multi-tasking button,camera button, a button on a physical keyboard, or any other physicalbutton on the device. In some embodiments, physical interactive elementscomprises interactive elements such as, for example, a switch or toggle,a wheel, a click wheel (e.g., iPod® click wheel), or any combinationthereof. In some embodiments, a user 100 interacts with the userinterface 113 by touching, tapping, swiping, or pressing any of the oneor more physical buttons located on the device outside of thetouchscreen.

In some embodiments, a device 102 includes various accessories 125 thatallow additional functionality. In some embodiments, the accessories 125include one or more of the following: microphone (e.g., for user voiceinteraction), a camera (e.g., for input of gestures commands or picturesfrom the user 100), speakers, one or more sensors such as a fingerprintreader or scanner, USB/micro-USB port, headphone jack, a card reader,SIM card slot, and any combination thereof.

FIG. 1B is a schematic diagram of one embodiment of a softwareapplication 108 for emergency calling. In some embodiments, the softwareapplication 108 comprises one or more software modules such as, forexample, a display module 141, an interface module 143, a communicationmodule 145, a sequence unlock module 147, an authentication module 149,or any combination thereof. In some embodiments, the display module 141displays an interactive graphic user interface on the touchscreen.

In some embodiments, the interface module 143 receives one or more userinteractions indicative of an emergency from the user interface 113 viaone or more inputs such as, for example, soft-buttons on thetouchscreen, hard buttons on the device outside of the touchscreen,commands spoken into a microphone 127, or any combination thereof. Insome embodiments, a user 100 interacts with the user interface 113 byproviding one or more user interactions indicative of an emergency inorder to send a request for an emergency assistance or response. In someembodiments, user interactions include interacting with the userinterface 113 by interacting with one or more non-physical interactiveelements (e.g., soft buttons on touchscreen), physical interactiveelements (e.g., hard buttons on device), or any combination thereof.

In some embodiments, user interactions indicative of an emergencycomprises a specific sequence of interactions. In some embodiments, userinteractions indicative of an emergency comprise interacting with atleast one physical interactive element, followed by interacting with atleast one non-physical interactive element. In some embodiments, userinteractions indicative of an emergency comprises interacting with atleast one non-physical interactive element, followed by interacting withat least one physical interactive element. In some embodiments, userinteractions indicative of an emergency comprise an interaction with anon-physical interactive element. In some embodiments, user interactionsindicative of an emergency comprises an interaction with a physicalinteractive element. In some embodiments, user interactions indicativeof an emergency comprise a sequence of interactions with a non-physicalinteractive element. In some embodiments, user interactions indicativeof an emergency comprise a sequence of interactions with a physicalinteractive element. In some embodiments, user interactions indicativeof an emergency comprise a sequence of interactions with at least onenon-physical interactive element.

In some embodiments, user interactions indicative of an emergencycomprise a sequence of interactions with at least 1, 2, 3, 4, 5, 6, 7,8, 9, or 10 or more non-physical interactive elements. In someembodiments, user interactions indicative of an emergency comprise asequence of interactions with at least one physical interactive element.In some embodiments, user interactions indicative of an emergencycomprise a sequence of interactions with at least 1, 2, 3, 4, 5, 6, 7,8, 9, or 10 or more physical interactive elements. In some embodiments,user interactions indicative of an emergency comprise a sequence ofinteractions with at least one non-physical interactive element and atleast one physical interactive element. In some embodiments, userinteractions indicative of an emergency comprise at least 1, 2, 3, 4, 5,6, 7, 8, 9, or 10 or more consecutive interactions with a physicalinteractive element. In some embodiments, user interactions indicativeof an emergency comprise pressing a hard button 1, 2, 3, 4, 5, 6, 7, 8,9, or 10 or more times consecutively. In some embodiments, userinteractions indicative of an emergency comprise at least 1, 2, 3, 4, 5,6, 7, 8, 9, or 10 or more consecutive interactions with at least 1, 2,3, 4, 5, 6, 7, 8, 9, or 10 or more physical interactive elements. Insome embodiments, user interactions indicative of an emergency compriseat least 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 or more consecutiveinteractions with at least 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 or more hardbuttons. In some embodiments, user interactions indicative of anemergency comprise at least 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 or moreconsecutive interactions with a non-physical interactive element. Insome embodiments, user interactions indicative of an emergency comprisepressing a soft button 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 or more timesconsecutively. In some embodiments, user interactions indicative of anemergency comprise at least 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 or moreconsecutive interactions with at least 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10or more non-physical interactive elements. In some embodiments, userinteractions indicative of an emergency comprise at least 1, 2, 3, 4, 5,6, 7, 8, 9, or 10 or more consecutive interactions with at least 1, 2,3, 4, 5, 6, 7, 8, 9, or 10 or more soft buttons. For example, in someembodiments, if at least 3 consecutive interactions with a soft button(e.g., a persistent emergency button) are indicative of an emergency,then a user presses the soft button 3, 4, 5, or more times in order forthe interface module 143 to receive (e.g., detect) interactionsindicative of an emergency. In some embodiments, separate interactionsare consecutive interactions if they are separated by no more than 100,200, 300, 400, 500, 600, 700, 800, 900, or 1000 milliseconds, includingincrements therein.

In some embodiments, user interactions indicative of an emergencycomprise pressing or touching a hard button continuously for apredefined period of time. In some embodiments, user interactionsindicative of an emergency comprise pressing or touching a hard buttoncontinuously for about 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 seconds or more.In some embodiments, user interactions indicative of an emergencycomprise pressing or touching a hard button continuously for at leastabout 1, 2, 3, 4, 5, 6, 7, 8, 9, or about 10 seconds or more. Forexample, in some embodiments, if pressing a hard button continuously forat least about 3 seconds is indicative of an emergency, then a userpresses the hard button continuously for 3, 4, 5 or more seconds inorder for the interface module 143 to receive (e.g., detect) userinteractions indicative of an emergency. In some embodiments, userinteractions indicative of an emergency comprise pressing or touching ahard button continuously for no more than about 1, 2, 3, 4, 5, 6, 7, 8,9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, or about 20 seconds. In someembodiments, user interactions indicative of an emergency comprisepressing or touching a soft button continuously for a predefined periodof time. In some embodiments, user interactions indicative of anemergency comprise pressing or touching a soft button continuously forabout 1, 2, 3, 4, 5, 6, 7, 8, 9, or about 10 seconds or more. In someembodiments, user interactions indicative of an emergency comprisepressing or touching a soft button continuously for at least about 1, 2,3, 4, 5, 6, 7, 8, 9, or about 10 seconds or more. In some embodiments,user interactions indicative of an emergency comprise pressing ortouching a soft button continuously for no more than about 1, 2, 3, 4,5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, or about 20seconds.

In some embodiments, a user 100 defines a sequence of interactionsindicative of an emergency. In some embodiments, the interface module143 allows a user to define one or more sequences of interactionsindicative of an emergency. For example, in some embodiments, the user100 defines a sequence of interactions indicative of an emergency, thesequence comprising: holding down the home button continuously for 5seconds. In some embodiments, the interface module 143 provides apredefined list of sequences of interactions indicative of an emergency.For example, in some embodiments, the interface module 143 provides apredefined sequence of interactions indicative of an emergency, thesequence comprising: pressing the physical home button three timesconsecutively. In some embodiments, a sequence of interactionsindicative of an emergency indicates a specific type of emergency. Forexample, in some embodiments, a sequence of interactions indicates afire emergency, a car crash, a police emergency, a medical emergency, ora combination thereof.

In some embodiments, a sequence of interactions indicative of anemergency comprises a combination of interactions using one or moreinteractive elements. In some embodiments, these sequences ofinteractions are provided by the device or predefined by a user. In someembodiments, the receipt of these interactions by the interface module143 causes the device communication module to send an emergency alert orinitiate the process for sending an emergency alert. In someembodiments, a sequence of interactions comprises touching a persistentemergency button on the touchscreen. In some embodiments, a sequence ofinteractions comprises pressing a home button (hard button) and thentouching a persistent emergency button (soft button). In someembodiments, sequence of interactions comprises pressing a home buttontwice, and then pressing an increase volume button twice. In someembodiments, a sequence of interactions comprises pressing a home buttontwice, and then pressing a decrease volume button twice. In someembodiments, a sequence of interactions comprises pressing a home buttoncontinuously for three seconds, and then touching a persistent emergencybutton. In some embodiments, a sequence of interactions comprisespressing a home button continuously for three seconds, and then givingaudio command requesting emergency assistance (via a microphone). Insome embodiments, a sequence of interactions comprises pressing a homebutton continuously for three seconds, and then making a gesturerequesting emergency assistance (via a camera). In some embodiments, asequence of interactions comprises giving an audio command requestingemergency assistance (via microphone), and then pressing a persistentemergency button on the touchscreen. In some embodiments, a sequence ofinteractions comprises giving an audio command requesting emergencyassistance (via a microphone), and then making a gesture requestingemergency assistance (via a camera). In some embodiments, a sequence ofinteractions comprises touching a persistent emergency button, and thentouching a soft button confirming the emergency. In some embodiments, asequence of interactions comprises touching a persistent emergencybutton, then touching a soft button indicating the type of emergency.

Authentication

In some embodiments, the authentication module 149 provides userauthentication. In some embodiments, authentication is needed toauthenticate the identity of the user or person who is providinginteractions indicative of an emergency to the communication device inorder to minimize the risk of unauthorized or accidental emergencyalerts. In some embodiments, the authentication module 149 evaluates ordetermines whether authentication is required for sending the emergencyalert. In some embodiments, the authentication module 149 decides thatauthentication is not required because the one or more user interactionsindicative of an emergency comprise a sequence that is unlikely to occurby accident. For example, in some embodiments, the authentication moduledetermines authentication is not required when the sequence of userinteractions indicative of an emergency comprises at least 1, 2, 3, 4,5, 6, 7, 8, 9, or 10 or more interactions. In some embodiments, theauthentication module determines authentication is not required when thesequence of user interactions indicative of an emergency comprisesinteracting with at least 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 or moreinteractive elements. In some embodiments, the interactive elements arephysical interactive elements, non-physical interactive elements, or anycombination thereof. In some embodiments, authentication is not requiredif the user provides authentication beforehand. For example, in someembodiments, a user links his fingerprint to his identity, address, andphone number on the communication device, and then providesauthentication by scanning his fingerprint on a fingerprint scanner onthe device. In some embodiments, the user 100 has predefined asufficiently secure sequence of user interactions (e.g., triple press onthe volume button), such that the risk of accidentally sending anemergency alert, request, or call is reduced or minimized even whenauthentication is not required. In some embodiments, the user is bestpositioned to know what sequence of interactions is more likely or lesslikely to occur by accident with regards to his or her communicationdevice. For example, in some embodiments, a user prefers to keep hercommunication device in her back pocket and realizes that her preferredmeans of carrying the device makes it likely the home button will bepressed continuously for a period of time (e.g., the “butt dial”).Keeping this in mind, the user decides to define a sequence ofinteractions comprising pressing the home button three consecutivetimes, followed by pressing a persistent emergency button on thetouchscreen. The user defines this sequence of interactions as beingsufficiently secure such that authentication is not required when theuser carries out the sequence of interactions to request emergencyassistance. Accordingly, in some embodiments, the user optionallyremoves or disables the authentication requirement for when theinterface module receives a particular sequence of interactionsindicative of an emergency. In some embodiments, user interactionsindicative of an emergency comprise one or more authenticatinginteractions. For example, in some embodiments, a sequence of userinteractions indicative of an emergency comprises triple pressing(pressing three consecutive times) a home button that comprises afingerprint scanner (e.g., the home button on an iPhone® 5S). In furtherembodiments, at least one of the three button presses is sufficient toprovide fingerprint authentication of the user.

In some embodiments, if authentication is required before a request foremergency assistance can be sent, the authentication module 149 providesuser authentication. In some embodiments, the user 100 interacts withthe device 102 to establish that he or she is the person associated withthe device and/or he or she is in an emergency situation. In someembodiments, user authentication is provided using a fingerprint reader,voice recognition, image recognition, password, pin, or any combinationthereof. In some embodiments, the user interaction providing userauthentication is selected from a group consisting of touch, tap, press,squeeze, swipe, voice, gesture, capturing a photo or video with thecamera, or any combination thereof.

Establishing Communication Link

In some embodiments, the communication module 145 uses the networkcomponent 123 of the device to send or receive communications, such asan emergency alert. In some embodiments, after the interface module 143receives one or more user interactions or a sequence of userinteractions indicative of an emergency, the communication module 145establishes a communication link with an emergency management service(EMS) or an emergency dispatch center (EDC). In some embodiments,establishing a communication link with an EMS or EDC comprises sendingan emergency alert. In some embodiments, an emergency alert comprises arequest for emergency assistance (e.g., an emergency request). In someembodiments, an emergency alert comprises emergency data. In someembodiments, emergency data is relevant to the emergency situation. Forexample, in some embodiments, relevant emergency data comprises locationinformation (e.g., GPS coordinates of the device), the type of emergency(e.g., as indicated by the user via the device), user identity, userinformation (e.g., user health information if this is a healthemergency), or any combination thereof. In some embodiments, emergencydata is sent to an EMS or EDC over an established communication linkafter the initial emergency alert has been sent.

In some embodiments, once a communication link has been established withan EMS or EDC, the device enters emergency mode. In some embodiments, adevice in emergency mode is characterized by an establishedcommunication link with an emergency management system or emergencydispatch center, wherein the display presents one or more interactivecommunication elements available for user selection to communicate withthe emergency management system or emergency dispatch center. In someembodiments, the one or more interactive communication elementscomprises a speechless button, wherein the communication module sendsinformation to the emergency management system or emergency dispatchcenter indicating the user is unable to speak upon user selection of thespeechless button. In some embodiments, the one or more interactivecommunication elements comprises a messaging button, wherein thecommunication module sends a message entered by a user to the emergencymanagement system or emergency dispatch center upon user selection ofthe messaging button. In some embodiments, the one or more interactivecommunication elements comprises a recording button for capturing andsending a photo or video to the emergency management system or emergencydispatch center upon user selection of the recording button. In someembodiments, the one or more interactive communication elementscomprises a speakerphone button for hands-free communication with theemergency management system or emergency dispatch center upon userselection of the speakerphone button.

Emergency Data

In some embodiments, the emergency alert comprises a request foremergency assistance. In some embodiments, the emergency alert furthercomprises location information. In some embodiments, the locationinformation comprises GPS coordinates provided by the location component117. In some embodiments, location information comprises coordinates ofthe cellular tower that transmitted the emergency alert. In someembodiments, location information comprises coordinates of the cellulartower the device sending the emergency alert was last in communicationwith. In some embodiments, the location information is saved informationin the EMS server associated with the user 100.

In some embodiments, emergency data comprises user information selectedfrom the group consisting of location (e.g., home or office address),emergency type (e.g., medical emergency, fire emergency, car crashemergency, or police emergency), speed and/or direction of the device102, health data of the user 100 (e.g., medical conditions andprescriptions), sensor data (e.g., physiological information provided bya wearable device for monitoring health) or any combination thereof. Insome embodiments, physiological information comprises heart rate orpulse, blood pressure, body temperature, hydration, blood cholesterol,blood glucose, other physiological characteristics, or any combinationthereof. In some embodiments, emergency data comprises historical userinformation. In some embodiments, historical user information isselected from location, previous emergencies, physiological data, or anycombination thereof. In some embodiments, emergency data comprisescurrent user information selected from current location, currentemergency type, current physiological data, or any combination thereof.In some embodiments, current user information comprises user informationthat is no more than 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 35, 40, 45,50, 55, 60 minutes old. In some embodiments, current user informationcomprises information that is no more than 1, 2, 3, 4, 5, 6, 7, 8, 9,10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, or 24 hours old.In some embodiments, current user information comprises information thatis no more than 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 days old. In someembodiments, historical user information comprises information that ismore than 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18,19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 35, 40, 45, 50, 55, 60minutes old. In some embodiments, historical user information comprisesinformation that is more than 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,14, 15, 16, 17, 18, 19, 20, 21, 22, 23, or 24 hours old. In someembodiments, historical user information comprises information that ismore than 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 days old. For example, insome embodiments, a sensor reading from a wearable device indicating apulse rate of 60 beats per minute for the user is current when it iscollected. However, in some embodiments, if historical data ispredefined as data that is more than 5 minutes old, then the sensorreading of 60 beats per minute will be categorized as historical dataafter 5 minutes have passed since the sensor reading was obtained.

FIG. 2 is an illustration of one embodiment of a communication device206. In some embodiments, the communication device 206 is a cellularphone, smart phone, portable computer, or wearable electronic device. Insome embodiments, the communication device 206 comprises a processor, amemory, a display 211, user interface 213, and an emergency callapplication 208 including instructions executable by the processor. Insome embodiments, the communication device 206 comprises a locationcomponent such as GPS. In some embodiments, on the display 211, thecommunication device 206 comprises one or more soft buttons that can beactivated by touch, for example, a soft button 214 displayed on a touchscreen display 211 when the device is in active mode. In someembodiments, the communication device 206 comprises one or more physicalbuttons 222, 224 (that may be interacted with by pressing or touching),for example, a power button, a volume rocker button or the menu buttonsactivated by touch such as those found on smart phones. In someembodiments, the communication device 206 comprises a microphone (notshown), a camera 242, and one or more sensors 232, for example, afingerprint reader. In some embodiments, the application 208 comprisesone or more software modules. In some embodiments, a software module isa user interface module, a communication module or an authenticationmodule. In some embodiments, the interface module receives one or moreuser interactions indicative of an emergency from the user interface, amicrophone (not shown), a camera 242, or one or more sensors 232 such asa fingerprint reader. In some embodiments, the communication moduleestablishes a communication link 272 with an EMS or an EDC 282. In someembodiments, communication module establishes a communication link 272with an EMS or EDC 282 by sending an emergency alert comprising arequest for emergency assistance and emergency data through thecommunication link. In some embodiments, the communication link 272 is adata connection through Wi-Fi, Bluetooth®, Infra-red (IR), the cellularnetwork, or other communication network. In some embodiments,authentication module is used to provide user authentication before thecommunication link 272 is established.

EMS and EDC

As referenced herein, an Emergency Management System (“EMS”) refers to asystem that receives and processes emergency alerts from users andforwards them to the EDC. Various embodiments of the EMS are describedin U.S. patent application Ser. No. 14/856,818, and incorporated hereinby reference. In some embodiments, when the emergency alert is sent fromthe communication device 206 to the EMS, it will forward the alert tothe appropriate EDC (such as a PSAP) which then provides an emergencyresponse or emergency assistance. In some embodiments, an emergencyresponse or emergency assistance comprises the EMS or EDC sendingemergency response personnel (e.g., firefighters, police, emergencymedical technicians, or any combination thereof).

The Emergency Dispatch Center (“EDC”) refers to the entity that receivesthe emergency alert and coordinates the emergency assistance. In someembodiments, EDC is a public organization run by the municipality,county or city or may be a private organization. In some embodiments,emergency assistance is selected from medical, caregivers, firefighting,police, military, paramilitary, border patrol, lifeguard, and securityservices. In some embodiments, the emergency alert is sent from thecommunication device 206 to an EDC, which will send the emergencyassistance. In some embodiments, an EDC comprises an EMS, wherein theEMS is a part of the EDC rather than an independent entity.

Active or Inactive Mode

In some embodiments, the communication device 206 is in one or morestates when an emergency arises that prompts a user to request emergencyassistance. For example, in some embodiments, when the communicationdevice 206 is powered ON, but in a hibernation or sleep state, thedisplay 211 is turned off. In some embodiments, regardless of the stateof the device, the device is in a device mode that allows a user send anemergency alert using a quick and simple process. In some embodiments,the device comprises at least two modes. In some embodiments, the devicecomprises two modes. In some embodiments, the device comprises threemodes. In some embodiments, the device comprises four modes. In someembodiments, the device comprises five modes. In some embodiments,device comprises at least 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 or moremodes. In some embodiments, device comprises an active mode. Active modeis characterized by the display being powered ON and presenting one ormore interactive elements. In some embodiments, the device comprises aninactive mode. Inactive mode is characterized by the display beingpowered OFF and presenting no interactive elements. In a particularembodiment, the device comprises both an active mode and an inactivemode. In some embodiments, the user 200 interacts with one or morephysical interactive elements on a device 206 in inactive mode toprovide one or more user interactions indicative of an emergency. Insome embodiments, the user 200 interacts with one or more hard buttons222, 224 on a device 206 in inactive mode to provide one or more userinteractions indicative of an emergency. In some embodiments, the user200 interacts with one or more soft buttons 214 on a device 206 inactive mode to provide one or more user interactions indicative of anemergency. In other embodiments, a user 200 is able to interact with oneor more hard buttons 222, 224 on a device 206 in active mode to provideone or more user interactions indicative of an emergency. In someembodiments, when the display is in inactive mode, the communicationdevice 206 is in one or more states of the device such as, for example,a sleep or hibernate state. In some embodiments, when the display is inactive mode, the communication device 206 is in one or more states ofthe device such as, for example, locked state, unlocked screen, flightstate, etc. Locked state refers to when the device is locked andinaccessible (e.g., user is unable to enter the right password).Unlocked screen refers to the device after it has been unlocked andaccessible (e.g., user entered the right password). Flight state refersto the device when communication is turned off (e.g., when the user hasboarded an airplane about to take off and is instructed to turn offcellular, Wi-Fi, and Bluetooth communication). In some embodiments, adevice sends an emergency alert upon receiving one or more userinteractions indicative of an emergency regardless of the state of thedevice. For example, in some embodiments, a device that receives one ormore user interactions indicative of an emergency while in anon-communicative state (e.g., flight or airplane state) immediatelyturns communication back on and attempts to send an emergency alert toan EMS or EDC. In some embodiments, a device comprises a stealth mode. Astealth mode is refers to a mode in which the emergency alert is madewithout detectable cues, for example, without sound. In someembodiments, a device in stealth mode has all sounds turned off, alertsturned off, vibrations turned off, the display turned off, or anycombination thereof. In some embodiments, a user optionally customizesthe stealth mode by choosing what to turn on or off during stealth mode.In some embodiments, a device is in either active mode or inactive modeand not both at the same time. In some embodiments, the device is instealth mode simultaneously with an active mode or inactive mode.

In some embodiments, a user 200 touches a soft button 214 to initiate anemergency alert. In comparison to a long and complex sequence ofinteractions such as turning on the display, unlocking the device,pressing the call button, dialing 9-1-1 (or another emergency numberthat is applicable in that jurisdiction) and pressing “send” or “call,”a one-touch button method of sending an emergency alert may be quickerand easier. In some embodiments, the display is in active mode, a meretouch of a button provides a quick and easy way to trigger the emergencyalert, which is especially useful when the user is suffering a medicalemergency. In some embodiments, a one-touch process for sending anemergency alert in a device in active mode is provided via a persistentemergency button that is omnipresent on the display screen throughoutall states of the active mode. Because time is of critical importance inresponding to emergency situations, having to carry out additional stepsin requesting emergency assistance can be a high burden for a user inthe middle of an emergency. Thus, there is a need for a way to requestemergency assistance regardless of the state of the communicationdevice. This need is met by the devices, systems, methods, and mediadisclosed herein. In some embodiments, a soft button 214 such as apersistent emergency button is available in different states of thecommunication device 206 (e.g., a phone in locked, unlocked screen,flight state, etc.) for user interaction to send an emergency alert.

In some embodiments, the interaction between the user 200 and thecommunication device 206 initiates a process for requesting emergencyassistance, and includes a sequence of actions or interactions. Forexample, in a particular embodiment, a first press of the soft button224 followed by a first press of the physical button 222 and a firstinteraction with the sensor 232 (e.g., providing user authentication viaa fingerprint scanner) initiates the emergency call. In someembodiments, the sequence of interactions between the user 200 and asoft button 214, one or more physical buttons 222, 224, and/or a sensor232 comprises one or more interactions with each of the soft button 214,physical button 224 and/or the sensor 232. In certain embodiments, thesequence of steps or interactions performed by the user 200 of thecommunication device 206 includes a gesture towards the camera 242 ofthe communication device 206. In some embodiments, the gesture towardsthe camera 229 is performed as a replacement to one or more interactionsin the sequence of interactions with the soft button 214, the physicalbuttons 222, 224, and/or the sensor 232 for sending an emergency alert.In some embodiments, the gesture towards the camera 229 is performed inaddition to a particular sequence of interactions with the soft button214, physical button 222, 224, and/or the sensor 232 for sending anemergency alert.

FIG. 3 is a schematic diagram of one embodiment of a communicationdevice 306 with a plurality of soft buttons 314 for making an emergencycall. In some embodiments, the plurality of soft buttons 314 for makingan emergency call comprises a six-tile soft button design. In someembodiments, the plurality of soft buttons 314 for making an emergencycall comprises a four-tile soft button design. In some embodiments, theplurality of soft buttons 314 for making an emergency call are accessedby interacting with or touching a persistent emergency button. In otherembodiments, interacting with or touching a persistent emergency buttonresults in sending an emergency alert without displaying the pluralityof soft buttons 314 for making an emergency call. In a particularembodiment, the communication device 306 comprises the followingcomponents—display 311, an emergency call application 308, physicalbuttons 322 and 324, camera 342 and fingerprint reader 332. In someembodiments, a user interaction that is indicative of an emergency is asoft touch with any one of the six soft buttons 314. In someembodiments, to indicate that there is fire and call emergency, a user200 may touch the fire indication button 326. In some embodiments, oneor more soft buttons for indicating different types of emergencies areselected from: Medical 328, Police 330, Car Crash 334, Water Emergency336 and Animal Rescue 338.

By sending an emergency alert comprising emergency data relevant to theemergency, a user 300 provides relevant information to the EMS/EDCand/or the emergency responders. For example, if the emergency alertcomprises information indicating a “Fire” emergency, then the EDC may beable to dispatch fire fighters to scene. On the other hand, if it is an“Animal Rescue”, the EDC may be able to dispatch animal control orrescue personnel to the location of the emergency. Previously, a personwho called for emergency assistance would have had to explain the typeof emergency help needed during the emergency call to the EDC. Instead,in some embodiments, a user 300 presses soft buttons 314 to both send anemergency alert and indicate the type of emergency help needed.Furthermore, in some embodiments, the emergency alert comprises locationinformation so the EDC is able to dispatch emergency responders withoutneeding to ask about the location of the user or the emergency. In thisway, according to some embodiments, a user 300 is able to initiate theemergency call and provide relevant details about the emergency using aone-touch process.

In some embodiments, when a user 300 interacts with a communicationdevice 306 to indicate an emergency using one of a plurality of softbuttons 314 (as shown in FIG. 3), an emergency alert is sent withone-touch. In some embodiments, a user 300 sends an emergency alertusing a one-touch process by touching a persistent emergency button onthe display of a device in active mode. FIG. 4 illustrates an exemplarymethod for making an emergency call with a one-touch process. First, theuser initiate the emergency call by touching one of several soft buttonsindicative of an emergency on the touchscreen display of a communicationdevice (act 412) or by touching a persistent emergency button. In otherembodiments, the emergency call is initiated by pressing one or morephysical buttons. In some embodiments, if the device is in an inactivemode where the display is OFF, pressing a hard button transforms thedevice from inactive to active mode, wherein the device in active modepresents one or more interactive elements (e.g., a persistent emergencybutton) for sending an emergency alert.

In some embodiments, initiating the emergency call or emergency alert412 causes a delay timer to start 414. The delay timer is a timer thatcounts down from a set amount of time. In some embodiments, delay timerrestarts whenever the user interacts with the display or device 414(e.g., by pressing or touching a hard or soft button). In someembodiments, the display on the device shows the delay timer inreal-time for a user to see how much time is left on the timer until theemergency alert is sent to an EMS or EDC. In some embodiments, thedisplay displays a cancel button for cancelling the emergency alertbefore the delay timer counts down to zero. In some embodiments, thedelay timer is chosen so that there is sufficient time for the user tocancel inadvertent calls, but not so long as to excessively delay theemergency response. In some embodiments, the delay timer is about 1, 2,3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22,23, 24, 25, 26, 27, 28, 29, 30, 35, 40, 45, 50, 55, or 60 seconds ormore, including increments therein. In some embodiments, the delay timeris at least about 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 35, 40, 45, 50,55, or 60 seconds or more, including increments therein. In someembodiments, the delay timer is no more than about 1, 2, 3, 4, 5, 6, 7,8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25,26, 27, 28, 29, 30, 35, 40, 45, 50, 55, or 60 seconds, includingincrements therein. In some embodiments, the delay timer is betweenabout 1 to 5 seconds, about 5-10 seconds, about 10-15 seconds, about15-20 seconds, about 20-25 seconds, about 25-30 seconds, about 30-35seconds, about 35-40 seconds, about 40-45 seconds, about 45-50 seconds,about 50-55 seconds, about 55-60 seconds, or more. In a particularembodiment, the delay timer is about 5 seconds. In another particularembodiment, the delay timer is about 8 seconds. In yet anotherparticular embodiment, the delay timer is about 10 seconds. In yetanother particular embodiment, the delay timer is about 12 seconds. Inyet another particular embodiment, the delay timer is about 15 seconds.In some embodiments, the delay timer is optionally customized bydefining a set time for the timer to count down from. For example, in aparticular embodiment, a user optionally customizes the delay timer bychoosing to set the timer at 10 seconds.

In some embodiments, while the delay timer is running or counting down(act 416), a user optionally confirms the emergency (act 418). In someembodiments, confirming the emergency causes the emergency module toimmediately send an emergency alert to an EDC or EMS. In someembodiments, the emergency alert comprises any available emergency data(act 422). In some embodiments, the display on the device presents thedelay timer and an emergency confirmation button after a user initiatesthe emergency call with a one-touch process. In some embodiments, theuser confirms the emergency by touching the emergency confirmationbutton before the delay timer finishes counting down to zero (act 418).In some embodiments, emergency data that is sent with the emergencyalert includes the type of emergency indication (such as Fire, Medical,etc.), location information, appropriate pre-saved user information(e.g., medical conditions or disabilities). In some embodiments, thelocation information includes GPS coordinates from the locationcomponent in the communication device. In some embodiments, if thecommunication device does not have a GPS or if the GPS signal is notavailable, historical GPS coordinates or user-inputted locationinformation is sent. In some embodiments, the method allows the user torefine the location information by confirming the location (e.g., theaddress indicated by current or historical GPS coordinates, a homeaddress, or a work address) as the location of the emergency 424. Insome embodiments, the user has saved information that is to be sent incase of emergencies, for example, disability information (such asdeafness, vision impairment, or some other physical handicap), ormedical conditions (such as heart conditions, allergies, diabetes,Alzheimer's, etc.).

In some embodiments, if the delay timer reaches zero 417 before the userconfirms the emergency, the device (or its communication module) sendsan emergency alert immediately 422. Thus, in one particular embodiment,if the user initiates the emergency call (e.g., sending an emergencyalert) by a one-touch process, the emergency request is sent after a10-second delay timer without any additional interactions. In someembodiments, the one-touch process comprises any single interaction witha physical or non-physical interactive element. For example, in oneparticular embodiment, a one-touch process comprises pressing the homebutton for at least 5 seconds. In some embodiments, a one-touch processcomprises pressing a persistent emergency button on the touchscreen. Inaddition, in some embodiments, with an additional touch (dual touch),the user is able to send the emergency call earlier by confirming (act418) the location information (act 424) further enhancing the emergencyalert. In some embodiments, a user sends an emergency alert by amulti-touch process (e.g., multiple interactions indicative of anemergency, wherein the interactions are touches). For example, in aparticular embodiment, a multi-touch process comprises pressing a homebutton two consecutive times to bring up a delay timer of 10 seconds. Inanother embodiment, a multi-touch process comprises pressing a homebutton and then touching a persistent emergency button. In someembodiments, a one-touch, two-touch (dual touch), or multi-touch processinitiates a delay timer as diagrammed in FIG. 4. In this way, a user isable to quickly and easily send an emergency alert while reducing therisk of sending an emergency alert by accident. In some embodiments, auser optionally customizes the sequence of interactions indicative of anemergency. Thus, in some embodiments, many multi-touch sequencevariations are possible for sending an emergency alert.

A one-touch or two-touch process for sending an emergency call isparticularly useful for several reasons. During emergencies, a user maybe occupied with dealing with the emergency situation, such as finding afire escape during a fire emergency. Alternatively, during a medicalemergency, the user may become physically compromised. If the user isable to send an emergency alert comprising an emergency request, thetype of emergency situation, and location information using a one-touchprocess, emergency response personnel can arrive at the scene fullyprepared based on the provided information without requiring furtheruser interactions. If the user has lost consciousness or is unresponsiveafter sending the emergency alert through the communication device,emergency responders may already have an idea of the cause of the user'sunresponsiveness and thus come prepared to deal with it. For example, auser may be suffering from a heart attack and sends an emergency alertusing a one-touch process by touching a “medical emergency” soft button.In some embodiments, the user has entered medical history informationincluding a history of heart problems into the software application forrequesting emergency assistance beforehand. In some embodiments, devicehas GPS. Therefore, in a particular embodiment, the emergency alertcomprises the emergency type (medical emergency), the locationinformation (GPS location of the communication device), and emergencydata (user medical history information). In some embodiments, even ifthe user becomes unresponsive due to the heart attack, the EMS or EDC isable to provide emergency response personnel with the relevantinformation received in the initial emergency alert as well as theuser's current unresponsiveness. The emergency response personnel maythen be prepared to attempt resuscitation of a heart attack victim whenthey arrive at the accident site. Thus, in some embodiments, emergencydata regarding the emergency is sent simultaneously with one-touch toenhance the emergency response.

The ease of one-touch or two-touch for sending the emergency call mustbe balanced with the risk of inadvertent and unauthorized calls. Toovercome this problem, user authentication may be required to reducerisk of abuse of the account by non-authorized users. In someembodiments, users are required to register in order to provideauthentication for sending emergency calls. In some embodiments, theuser registration process includes a verification step by SMS or text,email or a voice call requiring user input authenticating the identityof the user.

In some embodiments, the user interactions that are indicative of anemergency are chosen by a user or a service provider based on ease ofuse and having a lower chance of inadvertent calling. In someembodiments, the user chooses the trigger interaction based on personalpreferences or disabilities. Instead of using soft buttons, in someembodiments, a user with limited vision predefines the user interactionsindicative of an emergency as comprising voice commands, gestures, hardbutton interactions, or any combination thereof. In some embodiments,with voice command, both the initiation of the emergency call and theauthentication are done with voice recognition technology in oneinteraction (“one-command”).

In some embodiments, an emergency call, alert, or request sent using thedevices, systems, methods, or media described herein is sent to anEmergency Management System (“EMS”). In some embodiments, the finaldestination of the emergency call is an emergency dispatch center(“EDC”), such as Public Safety Answering Points (“PSAPs”) with the EMSacting as an intermediary that routes the initial emergency call, alert,or request to an appropriate EDC or PSAP based on location informationprovided in the emergency alert. In some embodiments, an emergency alertis sent to the EMS first if it is available, wherein the request is sentto an EDC or PSAP if an EMS is unavailable.

In some embodiments, prior to sending the emergency call, alert, orrequest to an EDC or PSAP, the EMS obtains the location for the user byvarious methods, for example, using GPS information from the usercommunication device, and connecting the location information with theassociated phone number. The EMS then queries a database at a VPC (VoIPPositioning Center) with the location information. In some embodiments,the VPC uses jurisdictional boundaries to determine the appropriate EDCor PSAP to route the call based on the location information. In aparticular embodiment, when the emergency call, alert, or request issent to the VPC, the VPC looks up the provisioned information andassigns an identification number called the Pseudo-Automatic NumberIdentification (pANI). In some embodiments, the VPC then forwards thecall to the appropriate PSAP. In some embodiments, the PSAP runs an ALI(automatic location information) query based on the pANI and the requestfor location information is sent back to the VPC database, which willretrieve and send the location information to the PSAP. In someembodiments, most of these steps occur within a few seconds so that theemergency call is sent quickly.

Because the information about the location of the user is of criticalimportance for routing to the correct PSAP and dispatching emergencyservices to the correct location, the disclosed method makes it possibleto send accurate location information. In comparison, in prior methodsfor sending location information when a mobile phone is used to send anemergency call through a carrier, the PSAPs receive limited locationinformation, which may lead to the call being sent to the incorrect PSAPand the emergency services being sent to the incorrect location. In mostcases, the PSAPs might only receive the address of the cell tower thatis routing the call, and they may or may not get the GPS location of thedevice after some delay. In some embodiments, the disclosed systems,devices, methods, and media ensure that the location information isaccurate by inserting the user's location information (e.g., GPScoordinates) when the emergency call is made and allowing the user toquickly confirm the location.

Disclosed herein are devices that include a persistent emergency buttonprovided for ease of calling within various states of the communicationdevice. In some embodiments, a persistent emergency button is a softbutton presented on the display of a communication device in activemode. FIG. 5 is a schematic diagram of one embodiment of a communicationdevice 506 with a soft button 514 for making an emergency call while thedisplay is showing the home screen. In some embodiments, thecommunication device 506 comprises a display 511, such as a touchscreencomprising a plurality of application icons 516, a notification bar 512,and a soft button 514 for sending an emergency call. In someembodiments, the user 500 interacts with the communication device 506using physical buttons 522, 524, a fingerprint reader 532, a camera 542,a microphone, or some other input source. As shown, in some embodiments,the soft button 514 are visible and responsive to user interaction (e.g.touch) on the home screen, even when the user 500 is not actively usingthe application 508 for requesting emergency assistance. In this way,the user 500 is able to send an emergency call with one-touch while thedisplay is showing the home screen.

In some embodiments, the persistent emergency button remains visible andresponsive when the device is in active mode even when a user isactively using an application. In some embodiments, the persistentemergency button remains visible and responsive when the device is inairplane state so long as the device is in active mode. In oneembodiment of the communication device 606 shown in FIG. 6, a persistentemergency button 614 for emergency calling is visible as an overlay ontop of a browser application. In some embodiments, the display 611 is atouchscreen with a plurality of interactive elements or icons forapplications 616, a notification bar 612 and a persistent emergencybutton 614 for sending an emergency call. In some embodiments, the user600 optionally interacts with the communication device 606 using thephysical buttons 622, 624, the fingerprint reader 632, the camera 642,the microphone 658 (not shown), etc. In some embodiments, the persistentemergency button 614 is visible and waiting for user interaction as anoverlay on top of the browser application 616 without blocking theaddress bar 618. In some embodiments, the location of the persistentemergency button is optionally customized. For example, in someembodiments, a user 600 optionally moves the persistent emergency buttonto a location of the user's choosing. In some embodiments, user 600optionally moves the persistent emergency button to a different locationdepending on the application that is open or the state of the device. Insome embodiments, because the persistent emergency button 614 is alwaysavailable in a device in active mode, the user 600 is able to send anemergency alert even within the browser application. In anotherembodiment, the persistent emergency button is an icon within thenotification bar 612, and drawing out the notification bar allowsone-touch emergency call. In some embodiments, the user 600 is able tosend an emergency alert by a one-touch or two-touch process using thepersistent emergency button as described above.

In some embodiments, the application 608 continues running inbackground. In some embodiments, the persistent emergency button isprogrammed as an overlay button. The application 608 is integrated intothe operating system of the communication device 606 to allow thepersistent emergency button to persist in all states of the device.

Many variations in the shape, size and position on the display of thepersistent emergency button are contemplated to incorporate ease of use,user preferences and disabilities, etc. In some embodiments, variationsare customizable by a user. In some embodiments, variations arepredefined by the device or application. In some embodiments, thepersistent emergency button is located within the top half of thedisplay or the bottom half of the display. In some embodiments, thepersistent emergency button is located on the left half of the displayor the right half of the display. In some embodiments, the persistentemergency button is located in the top left quadrant, the top rightquadrant, the bottom left quadrant, or the bottom right quadrant of thedisplay. In some embodiments, the persistent emergency button is locatedin the top center of the display, the bottom center of the display, orthe center of the display. In some embodiments, the persistent emergencybutton is a geometric shape selected from a circle, oval, square,triangle, rectangle, diamond, pentagon, hexagon, heptagon, octagon,nonagon, decagon, or star. In some embodiments, persistent emergencybutton comprises a shape with rounded corners. In some embodiments,persistent emergency button comprises a shape with sharp corners. Insome embodiments, persistent emergency button comprises one or morecolors selected from pink, red, orange, yellow, green, blue, purple,brown, cyan, indigo, violet, magenta, white, gray, black or other colorsproduced by any combination thereof. In addition, the persistentemergency button comprises multiple buttons comprising separate buttonsfor different types of emergencies.

FIG. 7 is a flowchart showing one embodiment of a user making anemergency call (or sending emergency alert) using one embodiment of thecommunication device wherein the sequence of user interactionsindicative of an emergency comprises a sequence of one or moreinteractions with one or more soft buttons and one or more interactionswith one or more hard buttons, along with a user authentication step. Insome embodiments, the display is in the active mode and waiting for theuser to interact with a soft button (e.g., button 616 in FIG. 6) on thetouch screen (act 712). When the user touches the soft button, thecommunication device registers this as the first step in a sequence ofinteractions indicative of an emergency and begins to compare it withone or more predefined sequences of soft button interactions indicativeof an emergency. Responsive to performance of the additionalinstructions, the device compares the sequence of interactions with oneor more sequences of soft button interactions predefined in the device(also referred to as “emergency call sequence”) (act 716). If there isno match (act 716), the device waits for the user to interact with thesoft button(s) again (act 712).

If there is a match between the user interaction and one or more softbutton interactions in the predefined sequence, the communication devicewaits for the user to confirm the request by interacting with one ormore physical buttons on the device (act 718). Responsive to the userinteraction with the physical button(s), the device compares thesequence of interactions with one or more sequences of hard buttoninteractions predefined in the device as indicative of an emergency(also referred to as “emergency call sequence”) (act 722). The devicewaits for the user to interact with the physical button(s) for apredefined time period (act 718). In some embodiments, if there is nomatch after a predefined maximum number of retries or expiry of apredefined time period (act 723), the device returns to the state it wasin prior to user interactions (act 712). If there is a match (act 722),the device waits for the user to interact with one or more sensors(e.g., a fingerprint scanner) to provide authentication (act 724).

If authentication is successful (act 727), the device sends an emergencyalert (act 726). Authentication is successful if the sensor readingmatches a pre-saved authorized reference. Following successfulauthentication, the device waits for a response from the EDC and informsthe user (act 732). During the length of the emergency, the device waitsfor further user interactions (act 734). If the authentication is notsuccessful (act 726), the device waits for the user to retryauthentication (act 724). In some embodiments, if authentication is notsuccessful after maximum retries or predefined time period, the devicereturns to the state it was in prior to user interactions (not shown).

In another embodiment (not shown), the authentication step using thesensor is not required. In some embodiments, user disables theauthentication step because he or she deems the soft and hard buttonuser interaction sequence to be sufficient to establish userauthentication. In this particular embodiment, if the physical buttonsequence matches interactions pre-saved in the device (act 722), theemergency call is placed immediately without requiring authentication(act 728).

FIG. 8 is a schematic diagram of one embodiment of the communicationdevice with a persistent emergency button in a locked screen. Thedisclosed device 806 includes a soft button 814 for making an emergencycall in the locked screen with a one-touch process as described in FIG.4. The communication device 806 comprises a display 811 such as, forexample, a touchscreen comprising a plurality of interactive elementsfor unlocking the phone 816, a notification bar 812, and a soft button814 for sending an emergency alert. In addition, in some embodiments,the user 800 is able to interact with the communication device 806 usingthe physical buttons 822, 824, 826, the fingerprint reader 832, thecamera 842, the microphone 858, or some other input source. In someembodiments, the physical buttons comprise a power button 826, a volumebutton 824, a home button 822, a navigation button, a keyboard button, areturn button, a multitasking button, a camera button, or anycombination thereof.

As shown, the soft button 814 may be visible and waiting for user touchin the locked screen, even if the user 800 has not entered the unlockcode. In this way, the user 800 may be able to send an emergency callwith one-touch from the locked screen when the device is in active modewith the display powered ON.

When the communicative device is in inactive mode, it may be a challengeto quickly and efficiently make an emergency call. If the device ispowered ON, the display may be turn off because of power savingsettings, which are user-defined or part of the operating system ormanufacturer customizations. In some embodiments, since the display isturned OFF when the device is in inactive mode, the emergency call isinitiated by pressing hard buttons such as 822, 824, or 826. In someembodiments, to prevent inadvertent calling, the sequence ofinteractions indicative of an emergency are chosen by the user orservice provider. For example, in a particular embodiment, a user orservice provider defines the sequence of interactions indicative of anemergency as comprising triple pressing the power button. Thus, in someembodiments, a sequence of presses such as a “triple press” of a hardbutton is sufficient to make an emergency call when the device is in aninactive state. In some embodiments, interacting with a hard buttontransforms the device from inactive mode to active mode and causes thedisplay to turn on and display one or more interactive elements such as,for example, a persistent emergency button. In some embodiments, a userpresses a hard button and then press a soft button such as a persistentemergency button as part of a process for sending an emergency alert(the alert may be sent immediately depending on whether a delay timer isinitiated and/or if authentication is required).

In some embodiments, an emergency call is made after a user interactswith hard buttons and then provides authentication. FIG. 9 is aflowchart showing how a user makes an emergency call with an inactivedisplay in one embodiment of the communication device. First, the userinitiates the emergency call by triple pressing the side physical buttonon the device (act 912). The user interaction causes the device tochange from inactive to active mode, which causes the display to turn ON(act 914).

In some embodiments, authentication (act 916) is not required (act 925)to send the emergency call (act 924). For example, in some embodiments,a user has predefined a sequence of user interactions to indicate anemergency (e.g., a particular voice command in user's voice, a sequenceof physical or soft button presses, a specific gesture, etc.). In someemergency situations, it is necessary to be able to make an emergencycall surreptitiously. In some embodiments, if the user has pre-defined aspecific sequence or pattern of interactions that is secure and unlikelyto be pressed inadvertently, the authentication module allows theemergency call without authentication.

In some embodiments, the user is experiencing an emergency and may notbe able to speak. In such embodiments, the user optionally providespredefined gestures and/or sequences of button presses and/or gesturesfor sending an emergency alert. In some embodiments, the authenticationmodule evaluates whether authentication is required if the risk ofinadvertent calls is low or the likelihood that the user is experiencinga real emergency. In some embodiments, a user or emergency serviceprovider (e.g., EMS, EDC, or PSAP) customizes the authentication processto require authentication or not require authentication. In someembodiments, the authentication module evaluates whether authenticationis required based on previously filled information by the user, forexample, the user's medical conditions, health information about theuser as detected by the sensors on the device (e.g., heart rate, pulse,temperature information detected by a wearable device), user's risk forunconsciousness, user's deviation from established habit, locationinformation, etc. In some embodiments, the authentication moduleevaluates whether authentication is required by querying whether theemergency service provider requires authentication.

In some embodiments, the user may be experiencing an emergency situationwhere he or she may not be able to press buttons (e.g., user is driving,user has some disability). In such situations, the user optionally sendsan emergency alert using a hands-free process through voice commands. Insome embodiments, voice analysis of the voice command providesauthentication for sending the emergency alert.

In some embodiments, the user may be required to authenticate that he orshe is authorized to make an emergency call from that device, forexample, by placing his or her finger on the fingerprint reader (act918). In some embodiments, if the authorization is successful based onsaved fingerprint of the user (act 918), an emergency alert is sent withemergency data (act 922). In this way, the user is able to send anemergency alert even with an inactive display. In some embodiments, adevice comprises at least two separate procedures for sending anemergency alert depending on the state of the device or the modes of thedisplay. For example, in some embodiments, when the display is OFF(device is in inactive mode), a physical button press sends theemergency alert. Conversely, in some embodiments, when the display is ON(device is in active mode), a persistent emergency button is availablein all or most of the device states for making an emergency call.

In some embodiments, if the authentication is unsuccessful, the user isrequired to provide his or her fingerprint again (act 918). It iscontemplated that there can be several variations to this scheme. Insome embodiments, a user provides authentication by interactions such astouch, tap, press, squeeze, swipe, voice, gesture, capturing a photo orvideo with the camera, or any combination thereof. For example, in someembodiments, the user's live video or photo captured by the camera isanalyzed by the authorization module through face recognition, bodyrecognition, audio recognition, or a combination thereof. In someembodiments, the user selects the interactions that are indicative of anemergency from a list of user interactions. In some embodiments, theuser interaction that initiates the emergency alert also providesauthentication, for example, voice command, image, video or throughsensors on the physical buttons. In some embodiments, a physical buttonis equipped with a biometric information reader for biometricauthentication. For example, in some embodiments, a physical button isequipped with a fingerprint reader to provide fingerprint authenticationwhen the user presses the button.

In some embodiments, the application 806 (see FIG. 8) allows the user todefine a sequence of interactions with physical interactive elements(e.g., hard buttons) to unlock the device and make the emergency call.In some embodiments, the application 806 uses third-party software tounlock the phone to make the emergency call.

In some embodiments, the authorization is performed or provided beforethe emergency call is initiated and it may be in the form ofverification (as described in discussion related to FIG. 3). In otherembodiments, the authorization step is completed after the emergencycall is initiated (as described in discussion related to FIGS. 7 and 9).

In one aspect, the disclosed herein is a method for transmitting arequest for assistance in an emergency situation, the method comprising:(a) receiving an indication of a first selection, by a user, of a softinterface of a communication device; (b) providing a response at theoutput interface of the communication device indicating the reception ofthe first selection by the communication device; (c) responsive to anindication of performance of the at least one instruction by the user,sending a request for emergency assistance from the communication deviceto a system connected with emergency assistance personnel including oneof an emergency management system (EMS), an emergency dispatch center(EDC), and another system connected with emergency assistance personnel;(d) determining if the request for emergency assistance has beenreceived by the emergency assistance personnel; (e) determining if thesystem connected with the emergency assistance personnel can be reachedby the communication device; (f) responsive to determining that therequest for emergency assistance has not been received by the emergencyassistance personnel within a predetermined time period, and that thesystem connected with the emergency assistance personnel can be reachedby the communication device, sending metadata including informationabout the user and a nature of the emergency situation, the metadatabeing one of provided by the user and sensed by the communicationdevice, to the system connected with the emergency assistance personnel;(g) responsive to determining that the system connected with theemergency assistance personnel cannot be reached by the communicationdevice, storing the metadata on the communication device and retrying toestablish communication with the system connected with the emergencyassistance personnel; and (h) responsive to establishing communicationwith the system connected with the emergency assistance personnel,sending the metadata to the emergency response personnel. In a furtherembodiment, the method comprises displaying the soft interface on atouch screen of a communication device, and receiving the indication ofthe first selection through the touch screen. In a further embodiment,the method comprises receiving the indication of the first selectionincludes receiving an indication of a single interaction with the softinterface. In a further embodiment, the method comprises receiving theindication of the first selection includes receiving an indication of amultiple interactions with the soft interface. In a further embodiment,the method comprises receiving the indication of the first selectionincludes receiving an indication of an input to one or more of touchscreen, a microphone, and a camera of the communication device. In afurther embodiment, the method comprises authenticating an identity ofthe user via interaction with a sensor on the communication device bythe user. In a further embodiment, the method comprises authenticatingthe identity of the user via interaction with a fingerprint sensor. In afurther embodiment, the method comprises authenticating the identity ofthe user via interaction with a heat sensor. In a further embodiment,the method comprises authenticating the identity of the user isperformed prior to receiving the indication of the first selection. In afurther embodiment, the method comprises a request for emergencyassistance is not sent from the communication device if the identity ofthe user has not been authenticated. In a further embodiment, the methodcomprises storing the metadata at the system connected with theemergency assistance personnel until the metadata is retrieved by theemergency response personnel. In a further embodiment, the methodcomprises sending a first type of request for emergency assistance bythe communication device in response to a first sequence of interactionswith user input interfaces of the communication device, and sending asecond type of request for emergency assistance by the communicationdevice in response to a second sequence of interactions with the userinput interfaces of the communication device. In a further embodiment,the method comprises the indication of performance of the at least oneinstruction by the user includes an indication of interaction with atleast one hard key of the communication device by the user. In a furtherembodiments, the method comprises the communication device receives theindication of a first selection, provides the response, receives theindication of performance of the at least one instruction by the user,and sends the request for emergency assistance from a non-active stateincluding one of a sleep state and a state wherein the screen is lockedand the phone is not performing any active communication for the user,without the user having to first unlock the communication device.

In one aspect, disclosed herein is a method for transmitting a requestfor assistance in an emergency situation, the method comprising: (a)receiving an indication of at least one selection of at least one hardinterface of a communication device, the at least one hard interfaceincluding one or more of a power button and a volume button of thecommunication device; (b) providing a response from the communicationdevice to the indication of at least one selection, the responseincluding an instruction for the user of the communication device; (c)responsive to receiving an indication of performance of the instructionby the user, authenticating the user by receiving an indication of aninteraction, by the user, with a sensor on the communication devicecapable of sensing one or more characteristics of the user; (d)responsive to receiving the indication of the at least one selection,receiving an indication of performance of the instruction, andauthenticating the user, sending a request for emergency assistance fromthe communication device to one of an emergency management system (EMS),an emergency dispatch center (EDC), and another system connected withemergency assistance personnel; (e) determining if the request foremergency assistance has been received by the one of the EMS, the EDC,and the another system; (f) determining if the one of the EMS, the EDC,and the another system can be reached by the communication device; (g)responsive to determining that the request for emergency assistance hasnot been received by the one of the EMS, the EDC, and the another systemwithin a predetermined time period, and that the one of the EMS, theEDC, and the another system can be reached by the communication device,sending metadata including information about the user and a nature ofthe emergency situation, the metadata being one of provided by the userand sensed by the communication device, to the one of the EMS, the EDC,and the another system; (h) responsive to determining that the one ofthe EMS, the EDC, and the another system cannot be reached by thecommunication device, storing the metadata on the communication deviceand retrying to establish communication with the one of the EMS, theEDC, and the another system; and (i) responsive to establishingcommunication with the one of the EMS, the EDC, and the another system,sending the metadata to the one of the EMS, the EDC, and the anothersystem. In one embodiment, the method comprises receiving an indicationof at least one selection of the at least one hard interface of thecommunication device includes receiving an indication of an interactionof the user with the power button. In a further embodiment, the methodcomprises receiving an indication of at least one selection of the atleast one hard interface of the communication device includes receivingan indication of an interaction of the user with the volume button.

In one aspect, disclosed herein is a communications device configured toreceive an input from a user, the communications device comprising auser interface, at least one physical interaction component, a locationdetermination module configured to send and receive messages over acommunications network; and a processor configured to: (i) receive anindication of a user interaction with one of the user interface and theat least one physical interaction component, and to detect a number oftimes an interaction occurred within a period of time and a duration ofeach interaction; (ii) receive an indication of a location of thecommunication device from the location determination module; (iii) placea call for emergency assistance to an EDC responsive to a sequence ofinteractions of the user with the communication device matching apre-determined pattern; and (iv) authenticate a user by interaction witha sensor on the communication device.

While preferred embodiments of the present invention have been shown anddescribed herein, it will be obvious to those skilled in the art thatsuch embodiments are provided by way of example only. Numerousvariations, changes, and substitutions will now occur to those skilledin the art without departing from the invention. It should be understoodthat various alternatives to the embodiments of the invention describedherein may be employed in practicing the invention. It is intended thatthe following claims define the scope of the invention and that methodsand structures within the scope of these claims and their equivalents becovered thereby.

Digital Processing Device

In some embodiments, the platforms, media, methods and applicationsdescribed herein include a digital processing device, a processor, oruse of the same. In further embodiments, the digital processing deviceincludes one or more hardware central processing units (CPU) that carryout the device's functions. In still further embodiments, the digitalprocessing device further comprises an operating system configured toperform executable instructions. In some embodiments, the digitalprocessing device is optionally connected a computer network. In furtherembodiments, the digital processing device is optionally connected tothe Internet such that it accesses the World Wide Web. In still furtherembodiments, the digital processing device is optionally connected to acloud computing infrastructure. In other embodiments, the digitalprocessing device is optionally connected to an intranet. In otherembodiments, the digital processing device is optionally connected to adata storage device.

In accordance with the description herein, suitable digital processingdevices include, by way of non-limiting examples, server computers,desktop computers, laptop computers, notebook computers, sub-notebookcomputers, netbook computers, netpad computers, set-top computers,handheld computers, Internet appliances, mobile smartphones, tabletcomputers, personal digital assistants, video game consoles, andvehicles. Those of skill in the art will recognize that many smartphonesare suitable for use in the system described herein. Those of skill inthe art will also recognize that select televisions, video players, anddigital music players with optional computer network connectivity aresuitable for use in the system described herein. Suitable tabletcomputers include those with booklet, slate, and convertibleconfigurations, known to those of skill in the art.

In some embodiments, the digital processing device includes an operatingsystem configured to perform executable instructions. The operatingsystem is, for example, software, including programs and data, whichmanages the device's hardware and provides services for execution ofapplications. Those of skill in the art will recognize that suitableserver operating systems include, by way of non-limiting examples,FreeBSD, OpenBSD, NetBSD®, Linux, Apple® Mac OS X Server®, Oracle®Solaris®, Windows Server®, and Novell® NetWare®. Those of skill in theart will recognize that suitable personal computer operating systemsinclude, by way of non-limiting examples, Microsoft® Windows®, Apple®Mac OS X®, UNIX®, and UNIX-like operating systems such as GNU/Linux®. Insome embodiments, the operating system is provided by cloud computing.Those of skill in the art will also recognize that suitable mobile smartphone operating systems include, by way of non-limiting examples, Nokia®Symbian® OS, Apple® iOS®, Research In Motion® BlackBerry OS®, Google®Android®, Microsoft® Windows Phone® OS, Microsoft® Windows Mobile® OS,Linux®, and Palm® WebOS®.

In some embodiments, the device includes a storage and/or memory device.The storage and/or memory device is one or more physical apparatusesused to store data or programs on a temporary or permanent basis. Insome embodiments, the device is volatile memory and requires power tomaintain stored information. In some embodiments, the device isnon-volatile memory and retains stored information when the digitalprocessing device is not powered. In further embodiments, thenon-volatile memory comprises flash memory. In some embodiments, thenon-volatile memory comprises dynamic random-access memory (DRAM). Insome embodiments, the non-volatile memory comprises ferroelectric randomaccess memory (FRAM). In some embodiments, the non-volatile memorycomprises phase-change random access memory (PRAM). In some embodiments,the non-volatile memory comprises magnetoresistive random-access memory(MRAM). In other embodiments, the device is a storage device including,by way of non-limiting examples, CD-ROMs, DVDs, flash memory devices,magnetic disk drives, magnetic tapes drives, optical disk drives, andcloud computing based storage. In further embodiments, the storageand/or memory device is a combination of devices such as those disclosedherein.

In some embodiments, the digital processing device includes a display tosend visual information to a subject. In some embodiments, the displayis a cathode ray tube (CRT). In some embodiments, the display is aliquid crystal display (LCD). In further embodiments, the display is athin film transistor liquid crystal display (TFT-LCD). In someembodiments, the display is an organic light emitting diode (OLED)display. In various further embodiments, on OLED display is apassive-matrix OLED (PMOLED) or active-matrix OLED (AMOLED) display. Insome embodiments, the display is a plasma display. In some embodiments,the display is E-paper or E ink. In other embodiments, the display is avideo projector. In still further embodiments, the display is acombination of devices such as those disclosed herein.

In some embodiments, the digital processing device includes an inputdevice to receive information from a subject. In some embodiments, theinput device is a keyboard. In some embodiments, the input device is apointing device including, by way of non-limiting examples, a mouse,trackball, track pad, joystick, game controller, or stylus. In someembodiments, the input device is a touch screen or a multi-touch screen.In other embodiments, the input device is a microphone to capture voiceor other sound input. In other embodiments, the input device is a videocamera or other sensor to capture motion or visual input. In furtherembodiments, the input device is a Kinect, Leap Motion, or the like. Instill further embodiments, the input device is a combination of devicessuch as those disclosed herein.

Non-Transitory Computer Readable Storage Medium

In some embodiments, the platforms, media, methods and applicationsdescribed herein include one or more non-transitory computer readablestorage media encoded with a program including instructions executableby the operating system of an optionally networked digital processingdevice. In further embodiments, a computer readable storage medium is atangible component of a digital processing device. In still furtherembodiments, a computer readable storage medium is optionally removablefrom a digital processing device. In some embodiments, a computerreadable storage medium includes, by way of non-limiting examples,CD-ROMs, DVDs, flash memory devices, solid state memory, magnetic diskdrives, magnetic tape drives, optical disk drives, cloud computingsystems and services, and the like. In some cases, the program andinstructions are permanently, substantially permanently,semi-permanently, or non-transitorily encoded on the media.

Computer Program

In some embodiments, the platforms, media, methods and applicationsdescribed herein include at least one computer program, or use of thesame. A computer program includes a sequence of instructions, executablein the digital processing device's CPU, written to perform a specifiedtask. Computer readable instructions may be implemented as programmodules, such as functions, objects, Application Programming Interfaces(APIs), data structures, and the like, that perform particular tasks orimplement particular abstract data types. In light of the disclosureprovided herein, those of skill in the art will recognize that acomputer program may be written in various versions of variouslanguages.

The functionality of the computer readable instructions may be combinedor distributed as desired in various environments. In some embodiments,a computer program comprises one sequence of instructions. In someembodiments, a computer program comprises a plurality of sequences ofinstructions. In some embodiments, a computer program is provided fromone location. In other embodiments, a computer program is provided froma plurality of locations. In various embodiments, a computer programincludes one or more software modules. In various embodiments, acomputer program includes, in part or in whole, one or more webapplications, one or more mobile applications, one or more standaloneapplications, one or more web browser plug-ins, extensions, add-ins, oradd-ons, or combinations thereof.

Web Application

In some embodiments, a computer program includes a web application. Inlight of the disclosure provided herein, those of skill in the art willrecognize that a web application, in various embodiments, utilizes oneor more software frameworks and one or more database systems. In someembodiments, a web application is created upon a software framework suchas Microsoft® .NET or Ruby on Rails (RoR). In some embodiments, a webapplication utilizes one or more database systems including, by way ofnon-limiting examples, relational, non-relational, object oriented,associative, and XML database systems. In further embodiments, suitablerelational database systems include, by way of non-limiting examples,Microsoft® SQL Server, mySQL™, and Oracle®. Those of skill in the artwill also recognize that a web application, in various embodiments, iswritten in one or more versions of one or more languages. A webapplication may be written in one or more markup languages, presentationdefinition languages, client-side scripting languages, server-sidecoding languages, database query languages, or combinations thereof. Insome embodiments, a web application is written to some extent in amarkup language such as Hypertext Markup Language (HTML), ExtensibleHypertext Markup Language (XHTML), or eXtensible Markup Language (XML).In some embodiments, a web application is written to some extent in apresentation definition language such as Cascading Style Sheets (CSS).In some embodiments, a web application is written to some extent in aclient-side scripting language such as Asynchronous Javascript and XML(AJAX), Flash® Actionscript, Javascript, or Silverlight®. In someembodiments, a web application is written to some extent in aserver-side coding language such as Active Server Pages (ASP),ColdFusion®, Perl, Java™, JavaServer Pages (JSP), Hypertext Preprocessor(PHP), Python™, Ruby, Tcl, Smalltalk, WebDNA®, or Groovy. In someembodiments, a web application is written to some extent in a databasequery language such as Structured Query Language (SQL). In someembodiments, a web application integrates enterprise server productssuch as IBM® Lotus Domino®. In some embodiments, a web applicationincludes a media player element. In various further embodiments, a mediaplayer element utilizes one or more of many suitable multimediatechnologies including, by way of non-limiting examples, Adobe® Flash®,HTML 5, Apple® QuickTime®, Microsoft® Silverlight®, Java™, and Unity®.

Mobile Application

In some embodiments, a computer program includes a mobile applicationprovided to a mobile digital processing device. In some embodiments, themobile application is provided to a mobile digital processing device atthe time it is manufactured. In other embodiments, the mobileapplication is provided to a mobile digital processing device via thecomputer network described herein.

In view of the disclosure provided herein, a mobile application iscreated by techniques known to those of skill in the art using hardware,languages, and development environments known to the art. Those of skillin the art will recognize that mobile applications are written inseveral languages. Suitable programming languages include, by way ofnon-limiting examples, C, C++, C#, Objective-C, Java™, Javascript,Pascal, Object Pascal, Python™, Ruby, VB.NET, WML, and XHTML/HTML withor without CSS, or combinations thereof.

Suitable mobile application development environments are available fromseveral sources. Commercially available development environmentsinclude, by way of non-limiting examples, AirplaySDK, alcheMo,Appcelerator®, Celsius, Bedrock, Flash Lite, .NET Compact Framework,Rhomobile, and WorkLight Mobile Platform. Other development environmentsare available without cost including, by way of non-limiting examples,Lazarus, MobiFlex, MoSync, and Phonegap. Also, mobile devicemanufacturers distribute software developer kits including, by way ofnon-limiting examples, iPhone and iPad (iOS) SDK, Android™ SDK,BlackBerry® SDK, BREW SDK, Palm® OS SDK, Symbian SDK, webOS SDK, andWindows® Mobile SDK.

Those of skill in the art will recognize that several commercial forumsare available for distribution of mobile applications including, by wayof non-limiting examples, Apple® App Store, Android™ Market, BlackBerry®App World, App Store for Palm devices, App Catalog for webOS, Windows®Marketplace for Mobile, Ovi Store for Nokia® devices, Samsung® Apps, andNintendo® DSi Shop.

Standalone Application

In some embodiments, a computer program includes a standaloneapplication, which is a program that is run as an independent computerprocess, not an add-on to an existing process, e.g., not a plug-in.Those of skill in the art will recognize that standalone applicationsare often compiled. A compiler is a computer program(s) that transformssource code written in a programming language into binary object codesuch as assembly language or machine code. Suitable compiled programminglanguages include, by way of non-limiting examples, C, C++, Objective-C,COBOL, Delphi, Eiffel, Java™, Lisp, Python™, Visual Basic, and VB .NET,or combinations thereof. Compilation is often performed, at least inpart, to create an executable program. In some embodiments, a computerprogram includes one or more executable complied applications.

Software Modules

In some embodiments, the platforms, media, methods and applicationsdescribed herein include software, server, and/or database modules, oruse of the same. In view of the disclosure provided herein, softwaremodules are created by techniques known to those of skill in the artusing machines, software, and languages known to the art. The softwaremodules disclosed herein are implemented in a multitude of ways. Invarious embodiments, a software module comprises a file, a section ofcode, a programming object, a programming structure, or combinationsthereof. In further various embodiments, a software module comprises aplurality of files, a plurality of sections of code, a plurality ofprogramming objects, a plurality of programming structures, orcombinations thereof. In various embodiments, the one or more softwaremodules comprise, by way of non-limiting examples, a web application, amobile application, and a standalone application. In some embodiments,software modules are in one computer program or application. In otherembodiments, software modules are in more than one computer program orapplication. In some embodiments, software modules are hosted on onemachine. In other embodiments, software modules are hosted on more thanone machine. In further embodiments, software modules are hosted oncloud computing platforms. In some embodiments, software modules arehosted on one or more machines in one location. In other embodiments,software modules are hosted on one or more machines in more than onelocation.

Databases

In some embodiments, the platforms, systems, media, and methodsdisclosed herein include one or more databases, or use of the same. Inview of the disclosure provided herein, those of skill in the art willrecognize that many databases are suitable for storage and retrieval ofbarcode, route, parcel, subject, or network information. In variousembodiments, suitable databases include, by way of non-limitingexamples, relational databases, non-relational databases, objectoriented databases, object databases, entity-relationship modeldatabases, associative databases, and XML databases. In someembodiments, a database is internet-based. In further embodiments, adatabase is web-based. In still further embodiments, a database is cloudcomputing-based. In other embodiments, a database is based on one ormore local computer storage devices.

Web Browser Plug-in

In some embodiments, the computer program includes a web browserplug-in. In computing, a plug-in is one or more software components thatadd specific functionality to a larger software application. Makers ofsoftware applications support plug-ins to enable third-party developersto create abilities which extend an application, to support easilyadding new features, and to reduce the size of an application. Whensupported, plug-ins enable customizing the functionality of a softwareapplication. For example, plug-ins are commonly used in web browsers toplay video, generate interactivity, scan for viruses, and displayparticular file types. Those of skill in the art will be familiar withseveral web browser plug-ins including, Adobe® Flash® Player, Microsoft®Silverlight®, and Apple® QuickTime®. In some embodiments, the toolbarcomprises one or more web browser extensions, add-ins, or add-ons. Insome embodiments, the toolbar comprises one or more explorer bars, toolbands, or desk bands.

In view of the disclosure provided herein, those of skill in the artwill recognize that several plug-in frameworks are available that enabledevelopment of plug-ins in various programming languages, including, byway of non-limiting examples, C++, Delphi, Java™, PHP, Python™, and VB.NET, or combinations thereof.

Web browsers (also called Internet browsers) are software applications,designed for use with network-connected digital processing devices, forretrieving, presenting, and traversing information resources on theWorld Wide Web. Suitable web browsers include, by way of non-limitingexamples, Microsoft® Internet Explorer®, Mozilla® Firefox®, Google®Chrome, Apple® Safari®, Opera Software® Opera®, and KDE Konqueror. Insome embodiments, the web browser is a mobile web browser. Mobile webbrowsers (also called mircrobrowsers, mini-browsers, and wirelessbrowsers) are designed for use on mobile digital processing devicesincluding, by way of non-limiting examples, handheld computers, tabletcomputers, netbook computers, subnotebook computers, smartphones, musicplayers, personal digital assistants (PDAs), and handheld video gamesystems. Suitable mobile web browsers include, by way of non-limitingexamples, Google® Android® browser, RIM BlackBerry® Browser, Apple®Safari®, Palm® Blazer, Palm® WebOS® Browser, Mozilla® Firefox® formobile, Microsoft® Internet Explorer® Mobile, Amazon® Kindle® Basic Web,Nokia® Browser, Opera Software® Opera® Mobile, and Sony® PSP™ browser.

While preferred embodiments of the present invention have been shown anddescribed herein, it will be obvious to those skilled in the art thatsuch embodiments are provided by way of example only. Numerousvariations, changes, and substitutions will now occur to those skilledin the art without departing from the invention. It should be understoodthat various alternatives to the embodiments of the invention describedherein may be employed in practicing the invention. It is intended thatthe following claims define the scope of the invention and that methodsand structures within the scope of these claims and their equivalents becovered thereby.

Example 1

John Doe is a third-year student at City University. Because finalexaminations are coming up, John is studying in the library until about2 a.m. Because he has walk through a high-crime area to reach hisapartment, John keeps his cellular phone handy in his pocket. John'sphone has been installed with an emergency calling software application,which includes a one-touch button for making an emergency call. John hasinstalled the application and saved his personal identificationinformation. John also used email verification to authenticate hiscellular phone number and connect it with his university email.

The emergency calling software application has a persistent button forone-touch calling that is available even when John's phone is outside ofthe application. Thus, there is a soft button that persists even whenJohn's phone is on the Home Screen or when he is in another applicationsuch as an Internet browser. In addition, John has predefined a sequenceof physical button interactions that will wake his phone and send anemergency call. He has chosen a five-button-press sequence of the volumetoggle button—Up, Down, Down, Down, Up, Down. Because the number ofphysical buttons interactions is more than three, the application'sauthentication module determines that the “risk of inadvertent calling”is low enough that there is no need for additional authentication suchas a soft-button press or fingerprint authentication. Because John isaware that his walk to the library is through an area with a high riskof mugging, he disables the 10 second delay for emergency calling suchthat the emergency call is sent immediately. In addition, John has putthe software on “stealth mode” where an emergency call is made silently.

Tonight, as John is walking past a park, he hears someone from behind “Ihave a gun. Give me your wallet.” John says, “I will give you money. Donot hurt me.” John takes out his wallet with one hand and with the othersurreptitiously enters the five-button-press for one-touch emergencycalling on his cellular phone that is in his pocket. Although the phonehas gone into a “Sleep” or “Hibernate” state where the display isswitched off (inactive mode), the emergency calling sequence of “Up,Down, Down, Down, Up, Down” is able to wake up the phone and make theemergency call.

An emergency call is sent to an EMS, which locates the appropriate EDC(such as a PSAP). Because there is no voice on the line, the EMS sendsan emergency alert with locational information (GPS coordinates of thephone) and will use voice simulation to transmit the information to thePSAP (because this PSAP can only receive voice information). Inaddition, the EMS sends an alert to the University police regarding anemergency situation at that location. Fortunately, a University policecar is in the vicinity and comes on the scene. Because of the one-touchemergency calling, John is able to recover his wallet from the mugger.

Example 2

Jane Doe is a retired school teacher in her eighties who lives alone.Jane is in good health for her age but has a medical condition thatmakes her susceptible to falls. At the insistence of her son Joe, Janeagrees to install an emergency calling software application on hercellular phone. Because Jane is susceptible to falls and may not be ableto reach her phone, Joe installs a Bluetooth® button and pairs it withthe application. Joe requests that her mother wear the blue-tooth buttonon a chain around her neck on days when she is not feeling well.

As part of the installation of the application, Joe goes through aprocess of SMS verification to connect the phone number with hismother's personal details. Joe also enters Jane's medical conditions anda list of medications into the application. The software evaluateswhether authentication will be necessary for one-touch emergency callingand finds that authentication is not necessary because of Jane's highrisk of falling.

One day, Jane wakes up feeling light-headed. Because of Joe's request,Jane puts on the chain with the Bluetooth® button around her neck andpairs the button with her phone. As she is walking to the bathroom, Janeexperiences a dizzy spell and falls down. During the fall, Jane bangsher head and starts bleeding. After the fall, Jane cannot move her legsbut she presses the Bluetooth® button for making an emergency call.Although the phone has gone into a “Sleep” or “Hibernate” mode where thedisplay is switched off, the Bluetooth® button is able to wake up thephone. Because Joe has set-up voice commands as part of the interactionsequence for indicating an emergency to send an emergency alert, theapplication requests Jane to provide a voice command by saying “Callemergency.” When Jane says “Call emergency”, the software matches hervoice to the one saved previously and makes the emergency call. Thevoice recognition also serves to provide user authentication, althoughin this case, the application has determined authentication is notrequired due to the Jane's high risk of falling.

The emergency call or request with locational information from the GPSof Jane's cell phone is now sent to an EMS, which identifies the correctEDC (such as a PSAP) to send the emergency alert to. The EMS then sendsthe emergency alert with GPS coordinates of Jane's phone in a formatthat the particular PSAP is capable of receiving. In addition tolocational information, the emergency alert includes information aboutJane's medical condition so that an ambulance is sent to Jane's homeimmediately. As a result, the paramedics reach Jane quickly and are ableto stop the bleeding. Jane receives appropriate medical treatment in ahospital and makes a speedy recovery.

Example 3

Mr. James Bond is working on an assignment late night at his office indowntown Manhattan. Mr. Bond's office is next to a chemical factory thatprocesses toxic chemicals. Mr. Bond is working on a special assignmentand suspects suspicious activities. Therefore, Mr. Bond pro-activelyinstalled a software application on his mobile communication device thatallows Mr. Bond to request emergency assistance and communicate in acovert fashion with an emergency management system. With thisapplication installed, Mr. Bond can press a sequence of hard buttons, asequence of soft buttons, or a combination thereof in order to send anemergency alert that initiates a communication session with an emergencymanagement system. In addition, Mr. Bond can perform a finger print scanin order to authenticate his identity for the emergency alert.

While Mr. Bond is working late at night finishing a report on animportant and critical assignment, Mr. Bond suspects something is notright. There is a distinct smell indicating a leak at the neighborhoodchemical factory. Toxic gases have escaped from their storage tanks, andMr. Bond has to quickly put on his gas mask, which he has kept nearbyfor such a calamity. Unfortunately, Mr. Bond is unable to talk into themobile device when wearing the gas mask. Mr. Bond picks up his mobilecommunication device and presses the decrease volume hard button locatedon the side of his communication device twice. This turns on thetouchscreen display, which presents a persistent emergency button, asoft button available in any state of the mobile communication devicewhenever the display is ON. This soft-button is available to Mr. Bondeven in the screen lock mode, allowing him to press this button withouthaving to unlock the screen. Mr. Bond presses the persistent emergencycall button. Next, he places his thumb against a fingerprint scanner onthe mobile communication device to scan his fingerprint, whichauthenticates his identity. This above process is predefined by Mr. Bondand the administrators of the emergency calling service. The emergencyalert is sent to the emergency management system, which establishes acommunication link with Mr. Bond's communication device. The alertcomprises both Mr. Bond's identification information and locationinformation according to his device's GPS.

The device is now in “emergency mode,” which was activated by thesending of the emergency alert. The emergency mode persists through thecourse of the communication link with the EMS and presents a pluralityof soft buttons on the touchscreen display comprising a buttonindicating the user cannot speak. Mr. Bond presses this button to signalto the EMS his inability to talk. He then presses a message button onthe touchscreen display and types out a message to the EMS explainingthe chemical leak. Mr. Bond also presses a photo/video button on thetouchscreen display to take and send a photo of the chemical leak. TheEMS coordinates the emergency response personnel and provides them withthe relevant information. The emergency response personnel are thus ableto arrive at the emergency location prepared with necessary equipmentfor diffusing the chemical leak. Mr. Bond in the meanwhile is able tomaintain himself in a safe location inside his office, while helpreaches. With timely help, Mr. Bond is able to evacuate to safety andeventually finish his assignment and hence save the world.

The sequence of hard button and soft button interactions (buttonpresses) along with fingerprint authentication on the communicationdevice allows Mr. Bond to place a call for emergency assistance withoutrequiring Mr. Bond to convey his emergency assistance request in a vocalmanner. Moreover, Mr. Bond is able to send pertinent information withthe request as well as during the resulting communication link,including GPS location coordinates, meta-data about Mr. Bond, andmultimedia information about the emergency situation that Mr. Bond iscontained in.

1. A device comprising at least one processor, a memory, a networkcomponent, a location component, a user interface, a display, andinstructions executable by the at least one processor to create anapplication for sending an emergency alert comprising: (a) an interfacemodule receiving from the user interface one or more user interactionsindicative of an emergency; (b) a communication module establishing acommunication link with an emergency management system and an emergencydispatch center after the interface module receives the one or more userinteractions indicative of an emergency, wherein establishing thecommunication link comprises sending an emergency alert comprising arequest for emergency assistance and emergency data comprising locationinformation; (c) an authentication module providing user authentication,wherein user authentication is required before sending the emergencyalert; and (d) at least two device modes comprising: (i) an active modecharacterized by the display being powered on and presenting one or morenon-physical interactive elements, wherein the one or more userinteractions indicative of an emergency comprises interacting with oneor more non-physical interactive elements on the display; and (ii) aninactive mode characterized by the display being powered off andpresenting no interactive elements, wherein the one or more userinteractions indicative of an emergency comprises interacting with oneor more physical interactive elements on the device; wherein a delaytimer is initiated after the interface module receives one or more userinteractions indicative of an emergency, wherein the communicationmodule sends the emergency alert when the delay timer counts down tozero.
 2. (canceled)
 3. The device of claim 1, wherein the displaypresents the delay timer as a countdown during which a user can cancelthe communication link before the countdown finishes.
 4. The device ofclaim 1, wherein the authentication module does not requireauthentication if the emergency management system and emergency dispatchcenter do not require authentication.
 5. The device of claim 1, whereinthe one or more user interactions indicative of an emergency ispredefined by a user.
 6. The device of claim 1, wherein the one or moreuser interactions indicative of an emergency provides userauthentication.
 7. The device of claim 1, wherein the active mode ischaracterized by the display presenting without interruption apersistent emergency button throughout a duration of the active mode,said persistent emergency button comprising at least one non-physicalinteractive element indicative of an emergency.
 8. The device of claim7, wherein the persistent emergency button is responsive to userinteraction when the device is locked.
 9. The device of claim 1, whereinthe device further comprises an emergency mode characterized by anestablished communication link with an emergency management system andemergency dispatch center, wherein the display presents one or moreinteractive communication elements available for user selection tocommunicate with the emergency management system and emergency dispatchcenter.
 10. The device of claim 1, wherein the one or more userinteractions indicative of an emergency is a one-touch interaction. 11.The device of claim 1, wherein the one or more user interactionsindicative of an emergency is a dual touch interaction.
 12. Anon-transitory computer-readable storage media encoded with a computerprogram including instructions executable by at least one processor tocreate an application for sending an emergency alert, the applicationcomprising: (a) an interface module receiving from a user interface ordisplay of a device one or more user interactions indicative of anemergency; (b) a communication module establishing a communication linkwith an emergency management system and an emergency dispatch centerafter the interface module receives the one or more user interactionsindicative of an emergency, wherein establishing the communication linkcomprises sending an emergency alert comprising a request for emergencyassistance and emergency data comprising location information; (c) anauthentication module providing user authentication, wherein userauthentication is required before the communication link is established;and (d) at least two device modes comprising: (i) an active modecharacterized by the display being powered on and presenting one or moreinteractive elements, wherein the one or more user interactionsindicative of an emergency comprises interacting with one or morenon-physical interactive elements on the display; and (ii) an inactivemode characterized by the display being powered off and presenting nointeractive elements, wherein the one or more user interactionsindicative of an emergency comprises interacting with one or morephysical interactive elements on the device; wherein a delay timer isinitiated after the interface module receives one or more userinteractions indicative of an emergency, wherein the communicationmodule sends the emergency alert when the delay timer counts down tozero.
 13. (canceled)
 14. The media of claim 12, wherein the displaypresents the delay timer as a countdown during which a user can cancelthe communication link before the countdown finishes.
 15. The media ofclaim 12, wherein the authentication module does not requireauthentication if the emergency management system and emergency dispatchcenter do not require authentication.
 16. The media of claim 12, whereinthe one or more user interactions indicative of an emergency ispredefined by a user.
 17. The media of claim 12, wherein the one or moreuser interactions indicative of an emergency provides userauthentication.
 18. The media of claim 12, wherein the active mode ischaracterized by the display presenting without interruption apersistent emergency button throughout a duration of the active mode,said persistent emergency button comprising at least one non-physicalinteractive element indicative of an emergency.
 19. The media of claim18, wherein the persistent emergency button is responsive to userinteraction when the device is locked.
 20. The media of claim 12,wherein the application further comprises an emergency modecharacterized by an established communication link with an emergencymanagement system and emergency dispatch center, wherein the displaypresents one or more interactive communication elements available foruser selection to communicate with the emergency management system andemergency dispatch center.
 21. The media of claim 12, wherein the one ormore user interactions indicative of an emergency is a one-touchinteraction.
 22. The media of claim 12, wherein the one or more userinteractions indicative of an emergency is a dual touch interaction. 23.A method of sending an emergency alert using a communication devicecomprising at least one processor, a memory, a network component, alocation component, a user interface, a display, and instructionsexecutable by the at least one processor to create an application forsending an emergency alert, the method comprising: (a) providing, by thedevice, an interface module receiving one or more user interactionsindicative of an emergency from the user interface or display; (b)establishing, by the device, a communication module establishing acommunication link with an emergency management system and an emergencydispatch center after the interface module receives the one or more userinteractions indicative of an emergency, wherein establishing thecommunication link comprises sending an emergency alert comprising arequest for emergency assistance and emergency data comprising locationinformation; (c) providing, by the device, an authentication moduleproviding user authentication, wherein user authentication is requiredbefore a communication link is established; and (d) providing, by thedevice, at least two device modes comprising: (i) an active modecharacterized by the display being powered on and presenting one or moreinteractive elements, wherein the one or more user interactionsindicative of an emergency comprises interacting with one or moreinteractive elements on the display; and (ii) an inactive modecharacterized by the display being powered off and presenting nointeractive elements, wherein the one or more user interactionsindicative of an emergency comprises interacting with one or more hardbuttons on the device; wherein a delay timer is initiated after theinterface module receives one or more user interactions indicative of anemergency, wherein the communication module sends the emergency alertwhen the delay timer counts down to zero.
 24. (canceled)
 25. The methodof claim 23, wherein the display presents the delay timer as a countdownduring which a user can cancel the communication link before thecountdown finishes.
 26. The method of claim 23, wherein theauthentication module does not require authentication if the emergencymanagement system and emergency dispatch center do not requireauthentication.
 27. The method of claim 23, wherein the active mode ischaracterized by the display presenting without interruption apersistent emergency button throughout a duration of the active mode,said persistent emergency button comprising at least one non-physicalinteractive element indicative of an emergency.
 28. The method of claim27, wherein the persistent emergency button is responsive to userinteraction when the device is locked.
 29. The method of claim 23,further comprising providing, by the device, an emergency modecharacterized by an established communication link with an emergencymanagement system and emergency dispatch center, wherein the displaypresents one or more interactive communication elements available foruser selection to communicate with the emergency management system andemergency dispatch center.
 30. (canceled)